Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jersey-dev] CI builds


The plan is to use Travis. As you know, Jersey tests take more than what is allowed to take in Travis. For this, we created a "smoke" profile, which takes only about 30 minutes to run. This is in pull request: Once the Travis is setup and able to run tests, and it would be possible to run the tests with pull requests, we can start dealing with pull requests, and be quite sure they do not break anything. Sounds good?

We would like to have Travis setup next week.



On 05.05.2018 13:08, Markus KARG wrote:

+1 for Travis

+1 for simply copying the solution we have set up in the JAX-RS API project


*From:*jersey-dev-bounces@xxxxxxxxxxx [mailto:jersey-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Christian Kaltepoth
*Sent:* Samstag, 5. Mai 2018 11:00
*To:* jersey-dev@xxxxxxxxxxx
*Subject:* [jersey-dev] CI builds

Hi all,

I'm very happy to see that the Jersey code is available in the EE4J repository now. And I'm even more excited to see that there are already 9 pull requests <> ready to be merged.

One important thing that is required for reviewing pull requests is to get some information about if the build (and the tests) still pass with the modified code. Therefore, I think it is very valuable to have automated CI builds for pull requests and branches.

I would like to propose to use Travis CI <> for getting CI builds for Jersey. Travis is super easy to set up and free to use for public repository. The EE4J JAX-RS API project recently enabled it for the JAX-RS API and it is working fine. We are even running the build including the test against different JDK versions (see here <>) which is one of the great features of Travis.

Adding Travis for Jersey is really simply and just requires two steps.

  * The Eclipse webmasters have to enable Travis CI builds for the
    eclipse-ee4j/jersey repository. This can be requested by creating
    corresponding ticket.
  * We need a single file called ".travis.yml" in the root of the
    repository. This file contains the Travis configuration and
    defines how to build the project. See the corresponding file
    from the eclipse-ee4j/jaxrs-api project for an example. I could
    contribute a working configuration via a pull request if you agree
    on my proposal.

What do you think?



Christian Kaltepoth




jersey-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top