[Geoserver-devel] Disabled *cite-* jobs on ares Jenkins

I have disabled all *cite-* jobs on ares Jenkins because changes required for the migration to apollo (build.geoserver.org) cause them all to fail.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

Hi Ben,
oh well, hopefully build.geoserver.org will have working jobs soon.
In the meantime I guess we’re flying blind… which will affect the maintenace
release of the 18th (2.11.3) but I guess not all that much, since it’s just getting
bug fixes.

By the way, is a volunteer needed for that release? I can help, but not the 18th,
guess I can start cutting the release around the 20th or 21th.

Cheers
Andrea

···

On Sat, Oct 14, 2017 at 12:38 AM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

I have disabled all cite- jobs on ares Jenkins because changes required for the migration to apollo (build.geoserver.org) cause them all to fail.

Kind regards,


Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-devel mailing list
Geoserver-devel@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Regards,

Andrea Aime

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

Ing. Andrea Aime
@geowolf
Technical Lead

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

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.

Hmm, were all of them failing?

The only changes that were made was an update of the cite-wfs-1.1 script, and re-adding a missing submodule to geoserver-cite-tools.

Based on this, I would only expect the various cite-wfs jobs to fail; the fact that all of them fail seems odd.

Based on the logs of these last failures, it seems like all the jobs are failing to resolve geoserver; I can’t see any error earlier in the logs as to why this might be the case.

With regards to the build.geoserver.org cite tests, we are a lot further along then we are before, but have run up against a failure coming out of the cite engine. If anyone more familiar with the cite tests could comment, that would be appreciated.

Torben

···

On Sat, Oct 14, 2017 at 1:07 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi Ben,
oh well, hopefully build.geoserver.org will have working jobs soon.
In the meantime I guess we’re flying blind… which will affect the maintenace
release of the 18th (2.11.3) but I guess not all that much, since it’s just getting
bug fixes.

By the way, is a volunteer needed for that release? I can help, but not the 18th,
guess I can start cutting the release around the 20th or 21th.

Cheers
Andrea


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-devel mailing list
Geoserver-devel@anonymised.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

On Sat, Oct 14, 2017 at 12:38 AM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

I have disabled all cite- jobs on ares Jenkins because changes required for the migration to apollo (build.geoserver.org) cause them all to fail.

Kind regards,


Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-devel mailing list
Geoserver-devel@anonymised.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Regards,

Andrea Aime

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

Ing. Andrea Aime
@geowolf
Technical Lead

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

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.

Torben,

it looks to me like the test engine is running before GeoServer is up:
https://build.geoserver.org/job/cite-wfs-1.1/1502/consoleText

I think the up-ness test is bad and tests only worked on ares because it was a slower machine and took time to build the suite. The test failure occurs before GeoServer is accepting connections. curl is probably successfully retrieving a Jetty error page.

Kind regards,
Ben.

On 17/10/17 12:33, Torben Barsballe wrote:

With regards to the build.geoserver.org cite tests, we are a lot further
along then we are before, but have run up against a failure coming out of
the cite engine. If anyone more familiar with the cite tests could comment,
that would be appreciated.

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
New Zealand

Andrea figured out the issue in the GeoServer meeting today - turns out that when I was getting the cite tests working on the new build server last week, the port number in /forms got changed. This is now fixed, and the ares cite tests are working again (except for wfs-1.1, which is expected). I have re-enabled all the jobs for now.

This might also be related to the failures on apollo, as I expect /forms also needs updating there. Looking into that now.

Torben

···

On Mon, Oct 16, 2017 at 5:37 PM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Torben,

it looks to me like the test engine is running before GeoServer is up:
https://build.geoserver.org/job/cite-wfs-1.1/1502/consoleText

I think the up-ness test is bad and tests only worked on ares because it was a slower machine and took time to build the suite. The test failure occurs before GeoServer is accepting connections. curl is probably successfully retrieving a Jetty error page.

Kind regards,
Ben.

On 17/10/17 12:33, Torben Barsballe wrote:

With regards to the build.geoserver.org cite tests, we are a lot further
along then we are before, but have run up against a failure coming out of
the cite engine. If anyone more familiar with the cite tests could comment,
that would be appreciated.


Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/>
New Zealand

On Tue, Oct 17, 2017 at 7:26 PM, Torben Barsballe <
tbarsballe@anonymised.com> wrote:

This might also be related to the failures on apollo, as I expect /forms
also needs updating there. Looking into that now.

I just had a very quick look and sort of concur with Ben, except one
thing... it certainly seems like it's doing the full loop
of curl calls much faster, but I'm seeing a "sleep 2" in there that should
make it wait 2 seconds... that does not
seem to be happening though... so maybe it's not faster, GeoServer is just
not starting?

And now I've noticed this:

+ ./startup.sh -Djetty.http.port=11010
+ (( i = 1 ))
+ (( i <= 100 ))
+ sleep 2*./run.sh: line 78: ./startup.sh: No such file or directory*

Uh?

Cheers
Andrea

--

Regards,

Andrea Aime

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

Ing. Andrea Aime
@geowolf
Technical Lead

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

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.