Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upCreate CI job for TravisCI #206
Comments
|
The intention of this issue is to have CI-build per pull-request so they are getting tested. See http://docs.travis-ci.com/user/pull-requests/ |
|
What is the quota for the builds on Travis? I think samples in current shape are putting too many WildFly copies all over the place :) I don't know Travis so it's a good reason to give it a spin if above is not a concern. |
|
You can do the same with CloudBees BuildHive as well.. just fyi. https://buildhive.cloudbees.com/ Or by simply configuring the Jenkins Git/GitHub plugins on the regular |
|
Sure, we can :) #207 |
|
Who is taking ownership of this issue then ? :) |
|
Feel free to assign #206 to me... I think I heard @bartoszmajsak volunteer for #207 ;) |
|
Issues assigned :) |
|
So are we leaving jenkins? |
|
Nope, I think @aheusingfeld wanted to have another CI job on Travis. |
|
Why have two? |
The only reason to go for Travis CI was that it has a perfect integration with Github's environment and supplies contributors with a more comprehensible report of pull-request builds. I didn't see something as understandable based on Jenkins, yet, - but that doesn't mean it doesn't exist. ;) If you like to set this up for Jenkins, please do. I don't know if I find the time to work on this before JAX next week. |
http://docs.travis-ci.com/user/build-configuration/#Build-Timeouts says:
Usually Travis doesn't talk of any other limitations but I heard that some Android builds which downloaded multiple SDK versions failed due to no free disk space errors. So #219 might also come in handy here - and on the build time of course. ;) |
|
I've enabled PR based builds in Jenkins as well. |
|
@johnament where did you add this? |
|
@aslakknutsen look at the ci jobs, you'll see two jobs that contain "pull-request". they're quirky, sometimes work. |
|
Aha.. Missed we swapped build server name :) |
|
I'm going to reassign this one to me since cloudbees dropped our FOSS account. |
|
Dropped? What you mean? |
|
This was imminent! Assigning to yourself is reasonable. On Tue Nov 04 2014 at 6:06:37 AM John Ament notifications@github.com
|
|
It's back: https://javaee-support.ci.cloudbees.com Now with TomEE jobs also. |
|
Wonder... @johnament - any particular reason why tomee-embedded is the default profile for the travis build? I'd rather go for either 'safe profile'(like wildfly-embedded) or go for build matrix
or drop travis completely in favour of cloudbees and (maybe) https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Plugin? |
|
+1 on wildfly-embedded, Tom EE is not Java EE 7 certified anyway. |
|
We switched to travis quite some time ago, so this can be closed I think. |
Alex Heusingfeld expressed interest in working on this.