[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [incubation] CI environments for GitHub PR build?
|
Hi Jeen,
For LocationTech GeoMesa, we are using Travis CI. Since GeoMesa
committers aren't GitHub admins, I believe we had to ask Eclipse
webmaster (or Andrea Ross, director of LT) to visit Travis-CI's website
and turn on the ability to run CI builds from the public Travis.
Travis CI is pretty good, but the free infrastructure is kinda slow, so
I wouldn't be opposed to having the ability to throw faster build boxes
at PRs...
Cheers,
Jim
On 8/10/2016 7:50 PM, Jeen Broekstra wrote:
What kind of Continuous Integration environments do Eclipse projects use?
I assume many projects use the preferred tool from the CBI, that is
Hudson (HIPP or shared instance), but I think I have seen several
projects mention other environments as well (e.g Jenkins or Travis).
I'm looking for a way to provide build/test support for Pull Requests
on GitHub: I'd like to be able to have our build service verify that a
PR doesn't break the build, _before_ we merge it.
I know Travis has support for this out of the box (and integrates very
nicely with GitHub), and Jenkins has a plugin for it, but I can't find
anything for Hudson in this space (nor any mention of whether the
Jenkins plugin is Hudson-compatible).
Any experiences from other projects would be most welcome. Have you
found a way to do this in a HIPP? Are you using Jenkins or Travis
instead? Pros/cons of each tool?
Cheers,
Jeen
_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation
