Create CI job for TravisCI

[arun-gupta]

Alex Heusingfeld expressed interest in working on this.

[aheusingfeld]

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/

[bartoszmajsak]

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.

[aslakknutsen]

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
instance.

[bartoszmajsak]

Sure, we can :) #207

[arun-gupta]

Who is taking ownership of this issue then ? :)

[aheusingfeld]

Feel free to assign #206 to me... I think I heard @bartoszmajsak volunteer for #207 ;)

[arun-gupta]

Issues assigned :)

[radcortez]

So are we leaving jenkins?

[arun-gupta]

Nope, I think @aheusingfeld wanted to have another CI job on Travis.

[aslakknutsen]

Why have two?

[arun-gupta]

@aheusingfeld ?

[aheusingfeld]

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.

[aheusingfeld]

What is the quota for the builds on Travis?

http://docs.travis-ci.com/user/build-configuration/#Build-Timeouts says:

With our current timeouts, a build will be terminated if it's still running after 50 minutes (respectively 70 on travis-ci.com), or if there hasn't been any log output in 10 minutes.

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. ;)

[johnament]

I've enabled PR based builds in Jenkins as well.

[aslakknutsen]

@johnament where did you add this?

[johnament]

@aslakknutsen look at the ci jobs, you'll see two jobs that contain "pull-request". they're quirky, sometimes work.

[aslakknutsen]

Aha.. Missed we swapped build server name :)

[johnament]

I'm going to reassign this one to me since cloudbees dropped our FOSS account.

[aslakknutsen]

Dropped? What you mean?

[arun-gupta]

This was imminent!

Assigning to yourself is reasonable.

On Tue Nov 04 2014 at 6:06:37 AM John Ament [email protected]
wrote:

I'm going to reassign this one to me since cloudbees dropped our FOSS
account.

—
Reply to this email directly or view it on GitHub
#206 (comment)
.

[radcortez]

It's back: https://javaee-support.ci.cloudbees.com

Now with TomEE jobs also.

[kubamarchwicki]

Wonder...

@johnament - any particular reason why tomee-embedded is the default profile for the travis build?
As it fails - it doesn't give a decent picture on PR.

I'd rather go for either 'safe profile'(like wildfly-embedded) or go for build matrix

env:
  matrix:
    - PROFILE=glassfish-embedded-arquillian
    - PROFILE=tomee-embedded-arquillian
    - PROFILE=wildfly-embedded-arquillian

script: "mvn clean install -P${PROFILE}"

or drop travis completely in favour of cloudbees and (maybe) https://wiki.jenkins-ci.org/display/JENKINS/GitHub+Plugin?

[arun-gupta]

+1 on wildfly-embedded, Tom EE is not Java EE 7 certified anyway.

[arjantijms]

We switched to travis quite some time ago, so this can be closed I think.