Hi all,
Currently the hudson jobs that build geotools and geoserver only build and test locally on the server, they do not deploy on every build. There has been discussion on changing this so that it does indeed upload every build.
The way I was thinking of doing this was setting up separate deploy jobs for each of the builds:
geoserver-2.0.x-deploy
geoserver-trunk-deploy
geotools-2.6.x-deploy
geotools-trunk-deploy
The jobs would "engage" as a post trigger to the regular build jobs. That way we don't run into problems with things being "half deployed". It also allows us to run a deploy directly without having to incur the cost of a full build (I intend to skip tests during the deploy jobs).
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
Hi all,
Currently the hudson jobs that build geotools and geoserver only build and test locally on the server, they do not deploy on every build. There has been discussion on changing this so that it does indeed upload every build.
The way I was thinking of doing this was setting up separate deploy jobs for each of the builds:
geoserver-2.0.x-deploy
geoserver-trunk-deploy
geotools-2.6.x-deploy
geotools-trunk-deploy
The jobs would "engage" as a post trigger to the regular build jobs. That way we don't run into problems with things being "half deployed". It also allows us to run a deploy directly without having to incur the cost of a full build (I intend to skip tests during the deploy jobs).
Well thought out.
+1 
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.