| Re: [jersey-dev] CI builds |
+1 for Travis +1 for simply copying the solution we have set up in the JAX-RS API project -Markus From: jersey-dev-bounces@xxxxxxxxxxx [mailto:jersey-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Kaltepoth 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.
What do you think? Christian |