[Geoserver-devel] Jenkins Notifications / Shutting down ares

GeoServer GeoServer Developer
1

Hello All,

I will be enabling notifications for all builds on build.geoserver.org, and disabling the corresponding jobs on ares.boundlessgeo.com.
If you are seeing excess notifications, this is probably why.

Torben

2

All notifications have now been turned on for build.geoserver.org, and the corresponding jobs on ares.boundlessgeo.com have been disabled, with the following exceptions:

geofence: All the geofence-*-nightly jobs are currently failing on build.geoserver.org. The issue seems to be in maven; from what I can determine some of the declared dependancies do not have valid artifacts available. This likely required a change in the pom (I expect ares may have has some jars manually installed in order for the build to work, although I have not been able to replicate this successful configuration).

geoscript: The geoscript.org build fails; it appears to depend on an old version of ant and maven, which are not available on build.geoserver.org. Either the build needs to be updated, or these should be installed on build.geoserver.org.

These to jobs are currently still enabled on both ares and build.geoserver.org.

Torben

···

On Fri, Nov 24, 2017 at 9:23 AM, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hello All,

I will be enabling notifications for all builds on build.geoserver.org, and disabling the corresponding jobs on ares.boundlessgeo.com.
If you are seeing excess notifications, this is probably why.

Torben

3

Hi,

geofence: All the geofence-*-nightly jobs are currently failing on
build.geoserver.org. The issue seems to be in maven; from what I can
determine some of the declared dependancies do not have valid artifacts
available. This likely required a change in the pom (I expect ares may have
has some jars manually installed in order for the build to work, although I
have not been able to replicate this successful configuration).

probably the valid artifacts were downloaded when they were available, and
then they remained available locally.
Looking into this.

   Cheers,
   Emanuele

Alle 01:37:57 di Saturday 25 November 2017, Torben Barsballe ha scritto:

All notifications have now been turned on for build.geoserver.org, and the
corresponding jobs on ares.boundlessgeo.com have been disabled, with the
following exceptions:

geofence: All the geofence-*-nightly jobs are currently failing on
build.geoserver.org. The issue seems to be in maven; from what I can
determine some of the declared dependancies do not have valid artifacts
available. This likely required a change in the pom (I expect ares may have
has some jars manually installed in order for the build to work, although I
have not been able to replicate this successful configuration).

geoscript: The geoscript.org build fails; it appears to depend on an old
version of ant and maven, which are not available on build.geoserver.org.
Either the build needs to be updated, or these should be installed on
build.geoserver.org.

These to jobs are currently still enabled on both ares and
build.geoserver.org.

Torben

On Fri, Nov 24, 2017 at 9:23 AM, Torben Barsballe <

tbarsballe@anonymised.com> wrote:
> Hello All,
>
> I will be enabling notifications for all builds on build.geoserver.org,
> and disabling the corresponding jobs on ares.boundlessgeo.com.
> If you are seeing excess notifications, this is probably why.
>
> Torben

4

Hi Torben,

(a previous reply of mine got lost somehow :|)

geofence: All the geofence-*-nightly jobs are currently failing on
build.geoserver.org. The issue seems to be in maven; from what I can

There are some problems in the local maven repo in jenkins, since the error is
about reading some local files (opening the zip/jar file and reading a pom file).

I modified the build configuration for geofence-master-nightly, setting the
"use private maven repository" option.
Once done that, maven did download again all the required dependencies, and
the build succedeed.
I could repeat this workaround for all the other failing jobs, but this would
not be optimal. I guess that getting into the system and deleting the bad files
would be the Good Thing to do.

   Cheers,
   Emanuele

Alle 01:37:57 di Saturday 25 November 2017, Torben Barsballe ha scritto:

All notifications have now been turned on for build.geoserver.org, and the
corresponding jobs on ares.boundlessgeo.com have been disabled, with the
following exceptions:

geofence: All the geofence-*-nightly jobs are currently failing on
build.geoserver.org. The issue seems to be in maven; from what I can
determine some of the declared dependancies do not have valid artifacts
available. This likely required a change in the pom (I expect ares may have
has some jars manually installed in order for the build to work, although I
have not been able to replicate this successful configuration).

geoscript: The geoscript.org build fails; it appears to depend on an old
version of ant and maven, which are not available on build.geoserver.org.
Either the build needs to be updated, or these should be installed on
build.geoserver.org.

These to jobs are currently still enabled on both ares and
build.geoserver.org.

Torben

On Fri, Nov 24, 2017 at 9:23 AM, Torben Barsballe <

tbarsballe@anonymised.com> wrote:
> Hello All,
>
> I will be enabling notifications for all builds on build.geoserver.org,
> and disabling the corresponding jobs on ares.boundlessgeo.com.
> If you are seeing excess notifications, this is probably why.
>
> Torben

--

Regards,
Emanuele Tajariol

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.

Ing. Emanuele Tajariol
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo
è consentito esclusivamente al destinatario del messaggio, per le finalità
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza
esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-
mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal
Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse,
costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the
attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act (Legislative
Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not
in accord with its purpose, any disclosure, reproduction, copying,
distribution, or either dissemination, either whole or partial, is strictly
forbidden except previous formal approval of the named addressee(s). If you
are not the intended recipient, please contact immediately the sender by
telephone, fax or e-mail and delete the information in this message that has
been received in error. The sender does not give any warranty or accept
liability as the content, accuracy or completeness of sent messages and
accepts no responsibility for changes made after they were sent or for other
risks which arise as a result of e-mail transmission, viruses, etc.

5

Fixing that maven problem, another interesting issue arose while building
GeoFence, concerning hibernate-spatial dependencies.
Since I guess it can be of general interest I'm linking it here:
   https://github.com/geoserver/geofence/issues/97

   Cheers,
   Emanuele

Alle 11:09:42 di Wednesday 6 December 2017, Emanuele Tajariol ha scritto:

Hi Torben,

(a previous reply of mine got lost somehow :|)

> geofence: All the geofence-*-nightly jobs are currently failing on
> build.geoserver.org. The issue seems to be in maven; from what I can

There are some problems in the local maven repo in jenkins, since the error
is about reading some local files (opening the zip/jar file and reading a
pom file).

I modified the build configuration for geofence-master-nightly, setting the
"use private maven repository" option.
Once done that, maven did download again all the required dependencies, and
the build succedeed.
I could repeat this workaround for all the other failing jobs, but this
would not be optimal. I guess that getting into the system and deleting
the bad files would be the Good Thing to do.

   Cheers,
   Emanuele

Alle 01:37:57 di Saturday 25 November 2017, Torben Barsballe ha scritto:
> All notifications have now been turned on for build.geoserver.org, and
> the corresponding jobs on ares.boundlessgeo.com have been disabled, with
> the following exceptions:
>
> geofence: All the geofence-*-nightly jobs are currently failing on
> build.geoserver.org. The issue seems to be in maven; from what I can
> determine some of the declared dependancies do not have valid artifacts
> available. This likely required a change in the pom (I expect ares may
> have has some jars manually installed in order for the build to work,
> although I have not been able to replicate this successful
> configuration).
>
> geoscript: The geoscript.org build fails; it appears to depend on an old
> version of ant and maven, which are not available on build.geoserver.org.
> Either the build needs to be updated, or these should be installed on
> build.geoserver.org.
>
> These to jobs are currently still enabled on both ares and
> build.geoserver.org.
>
> Torben
>
> On Fri, Nov 24, 2017 at 9:23 AM, Torben Barsballe <
>
> tbarsballe@anonymised.com> wrote:
> > Hello All,
> >
> > I will be enabling notifications for all builds on build.geoserver.org,
> > and disabling the corresponding jobs on ares.boundlessgeo.com.
> > If you are seeing excess notifications, this is probably why.
> >
> > Torben

--

Regards,
Emanuele Tajariol

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information.

Ing. Emanuele Tajariol
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i
file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo
è consentito esclusivamente al destinatario del messaggio, per le finalità
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza
esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-
mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal
Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse,
costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the
attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act (Legislative
Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use not
in accord with its purpose, any disclosure, reproduction, copying,
distribution, or either dissemination, either whole or partial, is strictly
forbidden except previous formal approval of the named addressee(s). If you
are not the intended recipient, please contact immediately the sender by
telephone, fax or e-mail and delete the information in this message that has
been received in error. The sender does not give any warranty or accept
liability as the content, accuracy or completeness of sent messages and
accepts no responsibility for changes made after they were sent or for other
risks which arise as a result of e-mail transmission, viruses, etc.

6

On Wed, Dec 6, 2017 at 2:09 AM, Emanuele Tajariol <etj@anonymised.com>
wrote:

Hi Torben,

(a previous reply of mine got lost somehow :|)

> geofence: All the geofence-*-nightly jobs are currently failing on
> build.geoserver.org. The issue seems to be in maven; from what I can

There are some problems in the local maven repo in jenkins, since the
error is
about reading some local files (opening the zip/jar file and reading a pom
file).

I modified the build configuration for geofence-master-nightly, setting the
"use private maven repository" option.
Once done that, maven did download again all the required dependencies, and
the build succedeed.
I could repeat this workaround for all the other failing jobs, but this
would
not be optimal. I guess that getting into the system and deleting the bad
files
would be the Good Thing to do.

I actually tried that when debugging the issue initially - when I deleted
the problematic jars from the maven repo, new jars with the same problem
just got downloaded (hence why I though it was an issue with the artifacts
themselves).

Perhaps one of the repos that the geofence build is pulling from has
corrupt artifacts?

Good to know that there is a workaround to get master building for now at
least.

Torben

   Cheers,
   Emanuele

Alle 01:37:57 di Saturday 25 November 2017, Torben Barsballe ha scritto:
> All notifications have now been turned on for build.geoserver.org, and
the
> corresponding jobs on ares.boundlessgeo.com have been disabled, with the
> following exceptions:
>
> geofence: All the geofence-*-nightly jobs are currently failing on
> build.geoserver.org. The issue seems to be in maven; from what I can
> determine some of the declared dependancies do not have valid artifacts
> available. This likely required a change in the pom (I expect ares may
have
> has some jars manually installed in order for the build to work,
although I
> have not been able to replicate this successful configuration).
>
> geoscript: The geoscript.org build fails; it appears to depend on an old
> version of ant and maven, which are not available on build.geoserver.org
.
> Either the build needs to be updated, or these should be installed on
> build.geoserver.org.
>
> These to jobs are currently still enabled on both ares and
> build.geoserver.org.
>
> Torben
>
> On Fri, Nov 24, 2017 at 9:23 AM, Torben Barsballe <
>
> tbarsballe@anonymised.com> wrote:
> > Hello All,
> >
> > I will be enabling notifications for all builds on build.geoserver.org
,
> > and disabling the corresponding jobs on ares.boundlessgeo.com.
> > If you are seeing excess notifications, this is probably why.
> >
> > Torben

--

Regards,
Emanuele Tajariol

GeoServer Professional Services from the experts! Visit
GeoSolutions Enterprise Support Services
for more information.

Ing. Emanuele Tajariol
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272

http://www.geo-solutions.it
x.com

-------------------------------------------------------
AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i
file/s allegato/i sono da considerarsi strettamente riservate. Il loro
utilizzo
è consentito esclusivamente al destinatario del messaggio, per le finalità
indicate nel messaggio stesso. Qualora riceviate questo messaggio senza
esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via
e-
mail e di procedere alla distruzione del messaggio stesso, cancellandolo
dal
Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte,
distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità
diverse,
costituisce comportamento contrario ai principi dettati dal D.Lgs.
196/2003.

The information in this message and/or attachments, is intended solely for
the
attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative
Decree June, 30 2003, no.196 - Italy's New Data Protection Code).Any use
not
in accord with its purpose, any disclosure, reproduction, copying,
distribution, or either dissemination, either whole or partial, is strictly
forbidden except previous formal approval of the named addressee(s). If you
are not the intended recipient, please contact immediately the sender by
telephone, fax or e-mail and delete the information in this message that
has
been received in error. The sender does not give any warranty or accept
liability as the content, accuracy or completeness of sent messages and
accepts no responsibility for changes made after they were sent or for
other
risks which arise as a result of e-mail transmission, viruses, etc.