Hi,
the Travis build I was talking about some time ago is currently up:
https://travis-ci.org/geoserver/geoserver
It’s building against OpenJDK7 and Oracle JDK7, and it’s currently broken
on a trivial issue on the WPS module.
I’ll try to fix it, but I have some doubts we’ll get a stable build out of this one.
The issue is, Travis does not seem to keep an artifact cache on disk, so in particular
the geotools artifacts are always fetched from the repos.
Now, this means the build may as well fetch out of date geotools jars, especially
in cases where the change is in geotools, but there is a geoserver dependency on that
change, either compile or testing wise.
Given that ares.boundlessgeo.com/jenkins build jobs (the one that do deploy on the repos)
are running every few hours, there is a solid chance we’ll get some spurious failures,
especially since Travis builds are triggered immediately after a github commit (within a minute
as far as I can see).
At the same time, we cannot have Travis builds deploy on the usual repos, since they
would deploy artifacts built with java 7.
Hum… suggestions?
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
Nice work setting this up! Unfortunately I can’t think of a great way to get around the build dependency issue either… but i would say a bit of instability in the build is worth the price of having a build on these JVMs given that the failures are relatively rare. I say we go with it for now and if we find it too problematic try to revisit.
···
On Sat, Sep 28, 2013 at 3:03 PM, Andrea Aime <andrea.aime@anonymised.com> wrote:
Hi,
the Travis build I was talking about some time ago is currently up:
https://travis-ci.org/geoserver/geoserver
It’s building against OpenJDK7 and Oracle JDK7, and it’s currently broken
on a trivial issue on the WPS module.
I’ll try to fix it, but I have some doubts we’ll get a stable build out of this one.
The issue is, Travis does not seem to keep an artifact cache on disk, so in particular
the geotools artifacts are always fetched from the repos.
Now, this means the build may as well fetch out of date geotools jars, especially
in cases where the change is in geotools, but there is a geoserver dependency on that
change, either compile or testing wise.
Given that ares.boundlessgeo.com/jenkins build jobs (the one that do deploy on the repos)
are running every few hours, there is a solid chance we’ll get some spurious failures,
especially since Travis builds are triggered immediately after a github commit (within a minute
as far as I can see).
At the same time, we cannot have Travis builds deploy on the usual repos, since they
would deploy artifacts built with java 7.
Hum… suggestions?
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
Vice President, Engineering | Boundless
jdeolive@anonymised.com
@j_deolive