Hi all,
it seems that the geoserver nightly build was failing because the geofence
project was not performing an "mvn deploy", so some deps could not be
satisfied. I edited the geofence jenkins configuration to fix this.
I also fixed an issue in the communityModule pom file concening the geofence
module. Once the snapshots are reloaded, the build should complete
successfully.
In order to put the geofence war file in the dist/ directory, the script in
the geofence build includes these lines:
dist=${WWW}/geofence/$ver
cp gui/web/target/geofence.war $dist/geofence-$ver-$datestamp-war.zip
The cp is failing because the geofence dist directory does not exist, and
needs to be created.
I commented out these lines in order to allow the job to finish successfully,
and will put them back once the directory is created.
Cheers,
Emanuele
--
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
Ing. Emanuele Tajariol
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 380 2116282
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
On Thu, Oct 16, 2014 at 8:29 AM, Emanuele Tajariol <etj@anonymised.com>
wrote:
Hi all,
it seems that the geoserver nightly build was failing because the geofence
project was not performing an "mvn deploy", so some deps could not be
satisfied. I edited the geofence jenkins configuration to fix this.
I also fixed an issue in the communityModule pom file concening the
geofence
module. Once the snapshots are reloaded, the build should complete
successfully.
In order to put the geofence war file in the dist/ directory, the script
in
the geofence build includes these lines:
dist=${WWW}/geofence/$ver
cp gui/web/target/geofence.war $dist/geofence-$ver-$datestamp-war.zip
The cp is failing because the geofence dist directory does not exist, and
needs to be created.
I commented out these lines in order to allow the job to finish
successfully,
and will put them back once the directory is created.
Directory created, and chowned to jenkins user so should be good to go.
Cheers,
Emanuele
--
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
Ing. Emanuele Tajariol
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 380 2116282
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
VP Engineering | Boundless <http://boundlessgeo.com/>
jdeolive@anonymised.com
@boundlessgeo <http://twitter.com/boundlessgeo/>
> Directory created, and chowned to jenkins user so should be good to go.
Thanks Justin!
GeoFence and related community module have been built and deployed properly in
latest run.
Cheers,
Emanuele
Alle 00:24:00 di Friday 17 October 2014, Justin Deoliveira ha scritto:
On Thu, Oct 16, 2014 at 8:29 AM, Emanuele Tajariol <etj@anonymised.com>
wrote:
> Hi all,
>
> it seems that the geoserver nightly build was failing because the
> geofence project was not performing an "mvn deploy", so some deps could
> not be satisfied. I edited the geofence jenkins configuration to fix
> this. I also fixed an issue in the communityModule pom file concening
> the geofence
> module. Once the snapshots are reloaded, the build should complete
> successfully.
>
> In order to put the geofence war file in the dist/ directory, the script
> in
>
> the geofence build includes these lines:
> dist=${WWW}/geofence/$ver
> cp gui/web/target/geofence.war $dist/geofence-$ver-$datestamp-war.zip
>
> The cp is failing because the geofence dist directory does not exist, and
> needs to be created.
> I commented out these lines in order to allow the job to finish
> successfully,
> and will put them back once the directory is created.
>
> Directory created, and chowned to jenkins user so should be good to go.
>
> Cheers,
> Emanuele
>
> --
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/NWWaa2 for more information.
> ==
>
> Ing. Emanuele Tajariol
> 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 380 2116282
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
>
> -------------------------------------------------------------------------
> ----- Comprehensive Server Monitoring with Site24x7.
> Monitor 10 servers for $9/Month.
> Get alerted through email, SMS, voice calls or mobile push notifications.
> Take corrective actions from your mobile device.
> http://p.sf.net/sfu/Zoho
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
Ing. Emanuele Tajariol
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 380 2116282
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------