Hi all,
So I just moved the nightly build stuff from a cron job on the build box to a proper hudson jobs:
http://hudson.opengeo.org/hudson/job/geoserver-1.7.x-nightly/
http://hudson.opengeo.org/hudson/job/geoserver-trunk-nightly/
The artifacts end up in the same place as they did before.
One annoying thing I could not get hudson to do was execute the part of the script that cleans out old artifacts. Kept on erroring out and I got frustrated using hudson over a slow connection 
So I left that part in the nightly cron job.
Anyways, another thing to note is that hudson will not bug us on the list when a nightly fails. So hopefully we won't run into the situation where nightly builds failing for days goes unnoticed.
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira wrote:
Anyways, another thing to note is that hudson will not bug us on the list when a nightly fails. So hopefully we won't run into the situation where nightly builds failing for days goes unnoticed.
Justin, I did not understand this. Did you mean it will bug us on the list?
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
Justin Deoliveira ha scritto:
Hi all,
So I just moved the nightly build stuff from a cron job on the build box to a proper hudson jobs:
http://hudson.opengeo.org/hudson/job/geoserver-1.7.x-nightly/
http://hudson.opengeo.org/hudson/job/geoserver-trunk-nightly/
The artifacts end up in the same place as they did before.
Great, thanks a lot for doing this. Making a test build for users
after fixing a bug just became so much easier
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Hi all,
So I just moved the nightly build stuff from a cron job on the build box to a proper hudson jobs:
http://hudson.opengeo.org/hudson/job/geoserver-1.7.x-nightly/
http://hudson.opengeo.org/hudson/job/geoserver-trunk-nightly/
The artifacts end up in the same place as they did before.
Great, thanks a lot for doing this. Making a test build for users
after fixing a bug just became so much easier
If you are even more impatient and want a live trunk build triggered by GT or GS svn changes:
https://cgsrv1.arrc.csiro.au/swrepo/GeoServerTrunk/latest/
These artifacts are the output of our GeoServerTrunk buildbot.
http://geobuilder.arrc.csiro.au/geoserver/builders/GeoT-java15
Build options:
geotools-trunk:
mvn -Djava.awt.headless=true -Dtest.maxHeapSize=256m -Dall clean install
geoserver-trunk:
mvn -Djava.awt.headless=true -Dtest.maxHeapSize=256m -Prelease clean install
geoserver assembly:
mvn assembly:attached
Note: no pom versions are changes, and no javadoc is built.No pretty Hudson weather report, either. :~-(
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
Ben Caradoc-Davies ha scritto:
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Hi all,
So I just moved the nightly build stuff from a cron job on the build box to a proper hudson jobs:
http://hudson.opengeo.org/hudson/job/geoserver-1.7.x-nightly/
http://hudson.opengeo.org/hudson/job/geoserver-trunk-nightly/
The artifacts end up in the same place as they did before.
Great, thanks a lot for doing this. Making a test build for users
after fixing a bug just became so much easier
If you are even more impatient and want a live trunk build triggered by GT or GS svn changes:
https://cgsrv1.arrc.csiro.au/swrepo/GeoServerTrunk/latest/
Interesting. Mind, this could result in quite some traffic hitting
your servers 
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Ben Caradoc-Davies ha scritto:
If you are even more impatient and want a live trunk build triggered by GT or GS svn changes:
https://cgsrv1.arrc.csiro.au/swrepo/GeoServerTrunk/latest/
Interesting. Mind, this could result in quite some traffic hitting
your servers
ESX cluster. Fattest backbone on the continent. Bring. It. On.
We have not even looked into archiving every build on our nearby petabyte datastore ...
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia
Ben Caradoc-Davies wrote:
Justin Deoliveira wrote:
Anyways, another thing to note is that hudson will not bug us on the list when a nightly fails. So hopefully we won't run into the situation where nightly builds failing for days goes unnoticed.
Justin, I did not understand this. Did you mean it will bug us on the list?
I mean that when a nightly build fails it will send an email to the developers list, just like when a regular build breaks.
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira wrote:
I mean that when a nightly build fails it will send an email to the developers list, just like when a regular build breaks.
Excellent! That means if I break a release pom, we will know about it.
Kind regards,
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer, CSIRO Exploration and Mining
Australian Resources Research Centre
26 Dick Perry Ave, Kensington WA 6151, Australia