[Geoserver-devel] GeoServer builds broken by failing geogig-master build

GeoServer GeoServer Developer
1

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x) are broken because the geogig-master build is failing and has not updated the 1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the GeoServer builds to fail. One of these checks had failed and three were still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the failing GeoServer Jenkins builds and all the Travis CI branch builds and pull request builds that failed because of this outage. I can help with this step.

Kind regards,

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

2

I am sorry Ben, it does not seem to be a good day for build servers - the LocationTech build server was troubled earlier in the day (timing out when Erik was trying to reach it).

I am going to go remove geogig from the ares build jobs as a temporary measure while this is resolved.

···

On 23 March 2017 at 17:54, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x) are broken because the geogig-master build is failing and has not updated the 1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the GeoServer builds to fail. One of these checks had failed and three were still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the failing GeoServer Jenkins builds and all the Travis CI branch builds and pull request builds that failed because of this outage. I can help with this step.

Kind regards,

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

–
Jody Garnett

3

Jody,

do you mean removing geogig from the communityRelease profile?

Kind regards,
Ben.

On 24/03/17 14:09, Jody Garnett wrote:

I am sorry Ben, it does not seem to be a good day for build servers - the
LocationTech build server was troubled earlier in the day (timing out when
Erik was trying to reach it).

I am going to go remove geogig from the ares build jobs as a temporary
measure while this is resolved.

--
Jody Garnett

On 23 March 2017 at 17:54, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x) are
broken because the geogig-master build is failing and has not updated the
1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the
GeoServer builds to fail. One of these checks had failed and three were
still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the
failing GeoServer Jenkins builds and all the Travis CI branch builds and
pull request builds that failed because of this outage. I can help with
this step.

Kind regards,

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

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

4

No I changed the jobs to say -PcommunityRelease,!geogig

···

On 23 March 2017 at 18:21, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Jody,

do you mean removing geogig from the communityRelease profile?

Kind regards,
Ben.

On 24/03/17 14:09, Jody Garnett wrote:

I am sorry Ben, it does not seem to be a good day for build servers - the
LocationTech build server was troubled earlier in the day (timing out when
Erik was trying to reach it).

I am going to go remove geogig from the ares build jobs as a temporary
measure while this is resolved.

–
Jody Garnett

On 23 March 2017 at 17:54, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x) are
broken because the geogig-master build is failing and has not updated the
1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the
GeoServer builds to fail. One of these checks had failed and three were
still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the
failing GeoServer Jenkins builds and all the Travis CI branch builds and
pull request builds that failed because of this outage. I can help with
this step.

Kind regards,

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

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

–
Jody Garnett

5

Sigh it did not work, I escaped the bang and everything:

mvn -f src/community/pom.xml -B -U -DskipTests -PcommunityRelease,\!geogig clean install -DconfigDirectory=../../../data -T2 -fae

Next step as you say is removing geogig from the communityRelease so you can work today.

···

On 23 March 2017 at 18:58, Jody Garnett <jody.garnett@anonymised.com> wrote:

No I changed the jobs to say -PcommunityRelease,!geogig

–
Jody Garnett

–
Jody Garnett

On 23 March 2017 at 18:21, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Jody,

do you mean removing geogig from the communityRelease profile?

Kind regards,
Ben.

On 24/03/17 14:09, Jody Garnett wrote:

I am sorry Ben, it does not seem to be a good day for build servers - the
LocationTech build server was troubled earlier in the day (timing out when
Erik was trying to reach it).

I am going to go remove geogig from the ares build jobs as a temporary
measure while this is resolved.

–
Jody Garnett

On 23 March 2017 at 17:54, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x) are
broken because the geogig-master build is failing and has not updated the
1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the
GeoServer builds to fail. One of these checks had failed and three were
still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the
failing GeoServer Jenkins builds and all the Travis CI branch builds and
pull request builds that failed because of this outage. I can help with
this step.

Kind regards,

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

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

6

My apologies. I merged the changes in GeoServer before I realized the LocationTech build server wasn’t properly building GeoGig. Trying to get things in too eagerly. I will not do that again.

If the geogig module hasn’t already been removed from the communityRelease list, I can make that change now, until the LocationTech build servers are functioning again.

Again, my sincerest apologies,

···

On Thu, Mar 23, 2017 at 9:00 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Sigh it did not work, I escaped the bang and everything:

mvn -f src/community/pom.xml -B -U -DskipTests -PcommunityRelease,\!geogig clean install -DconfigDirectory=../../../data -T2 -fae

Next step as you say is removing geogig from the communityRelease so you can work today.

Erik Merkle
Software Engineer | Boundless

–
Jody Garnett

On 23 March 2017 at 18:58, Jody Garnett <jody.garnett@anonymised.com> wrote:

No I changed the jobs to say -PcommunityRelease,!geogig

–
Jody Garnett

On 23 March 2017 at 18:21, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Jody,

do you mean removing geogig from the communityRelease profile?

Kind regards,
Ben.

On 24/03/17 14:09, Jody Garnett wrote:

I am sorry Ben, it does not seem to be a good day for build servers - the
LocationTech build server was troubled earlier in the day (timing out when
Erik was trying to reach it).

I am going to go remove geogig from the ares build jobs as a temporary
measure while this is resolved.

–
Jody Garnett

On 23 March 2017 at 17:54, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x) are
broken because the geogig-master build is failing and has not updated the
1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the
GeoServer builds to fail. One of these checks had failed and three were
still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the
failing GeoServer Jenkins builds and all the Travis CI branch builds and
pull request builds that failed because of this outage. I can help with
this step.

Kind regards,

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

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

7

Thanks for trying, Jody. My main concern is the loss of continuous integration and impact on Travis CI for pull requests. I am not submitting or merging pull requests today so am not yet personally affected.

As an aside, the Maven option that works for me is "-pl", which can be used to exclude a module by giving its path relative to the top-level pom. I use it to exclude app-schema oracle online tests. In the geogig case below, this would be:

-pl '!geogig'

However, I do not think that we should modify all the Jenkins and Travis CI builds as we will only have to change them all back, and community modules that do not compile are not permitted in the communityRelease profile. We should not need magic options to build.

When do we expect to see a successful geogig-master build? If we are likely to get one in the next 12 hours, we should just wait, otherwise we should remove geogig from the communityRelease profile on all affected branches.

Kind regards,
Ben.

On 24/03/17 15:00, Jody Garnett wrote:

Sigh it did not work, I escaped the bang and everything:

mvn -f src/community/pom.xml -B -U -DskipTests
-PcommunityRelease,\!geogig clean install
-DconfigDirectory=../../../data -T2 -fae

Next step as you say is removing geogig from the communityRelease so you
can work today.

--
Jody Garnett

On 23 March 2017 at 18:58, Jody Garnett <jody.garnett@anonymised.com> wrote:

No I changed the jobs to say -PcommunityRelease,!geogig

--
Jody Garnett

On 23 March 2017 at 18:21, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Jody,

do you mean removing geogig from the communityRelease profile?

Kind regards,
Ben.

On 24/03/17 14:09, Jody Garnett wrote:

I am sorry Ben, it does not seem to be a good day for build servers - the
LocationTech build server was troubled earlier in the day (timing out
when
Erik was trying to reach it).

I am going to go remove geogig from the ares build jobs as a temporary
measure while this is resolved.

--
Jody Garnett

On 23 March 2017 at 17:54, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x) are
broken because the geogig-master build is failing and has not updated
the
1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the
GeoServer builds to fail. One of these checks had failed and three were
still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the
failing GeoServer Jenkins builds and all the Travis CI branch builds and
pull request builds that failed because of this outage. I can help with
this step.

Kind regards,

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

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

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

8

Yes, please, Erik. As discussed in my other email, unless you expect a successful geogig-master build in the next few hours, please remove geogig from the communityRelease profile on all affected branches.

Kind regards,
Ben.

On 24/03/17 16:13, Erik Merkle wrote:

My apologies. I merged the changes in GeoServer before I realized the
LocationTech build server wasn't properly building GeoGig. Trying to get
things in too eagerly. I will not do that again.

If the geogig module hasn't already been removed from the communityRelease
list, I can make that change now, until the LocationTech build servers are
functioning again.

Again, my sincerest apologies,

Erik Merkle
Software Engineer | Boundless <http://boundlessgeo.com/&gt;

<http://d32wfbeasdaw38.cloudfront.net/img/Boundless_Logo.png&gt;

On Thu, Mar 23, 2017 at 9:00 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

Sigh it did not work, I escaped the bang and everything:

mvn -f src/community/pom.xml -B -U -DskipTests -PcommunityRelease,\!geogig clean install -DconfigDirectory=../../../data -T2 -fae

Next step as you say is removing geogig from the communityRelease so you
can work today.

--
Jody Garnett

On 23 March 2017 at 18:58, Jody Garnett <jody.garnett@anonymised.com> wrote:

No I changed the jobs to say -PcommunityRelease,!geogig

--
Jody Garnett

On 23 March 2017 at 18:21, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Jody,

do you mean removing geogig from the communityRelease profile?

Kind regards,
Ben.

On 24/03/17 14:09, Jody Garnett wrote:

I am sorry Ben, it does not seem to be a good day for build servers -
the
LocationTech build server was troubled earlier in the day (timing out
when
Erik was trying to reach it).

I am going to go remove geogig from the ares build jobs as a temporary
measure while this is resolved.

--
Jody Garnett

On 23 March 2017 at 17:54, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x)
are
broken because the geogig-master build is failing and has not updated
the
1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the
GeoServer builds to fail. One of these checks had failed and three were
still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the
failing GeoServer Jenkins builds and all the Travis CI branch builds
and
pull request builds that failed because of this outage. I can help with
this step.

Kind regards,

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

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

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

9

Oh, and I see from the Jenkins notifications that Jody has already removed geogig and the builds are recovering. Thanks!

Kind regards,
Ben.

On 24/03/17 16:24, Ben Caradoc-Davies wrote:

Yes, please, Erik. As discussed in my other email, unless you expect a
successful geogig-master build in the next few hours, please remove
geogig from the communityRelease profile on all affected branches.

Kind regards,
Ben.

On 24/03/17 16:13, Erik Merkle wrote:

My apologies. I merged the changes in GeoServer before I realized the
LocationTech build server wasn't properly building GeoGig. Trying to get
things in too eagerly. I will not do that again.

If the geogig module hasn't already been removed from the communityRelease
list, I can make that change now, until the LocationTech build servers are
functioning again.

Again, my sincerest apologies,

Erik Merkle
Software Engineer | Boundless <http://boundlessgeo.com/&gt;

<http://d32wfbeasdaw38.cloudfront.net/img/Boundless_Logo.png&gt;

On Thu, Mar 23, 2017 at 9:00 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

Sigh it did not work, I escaped the bang and everything:

mvn -f src/community/pom.xml -B -U -DskipTests -PcommunityRelease,\!geogig clean install -DconfigDirectory=../../../data -T2 -fae

Next step as you say is removing geogig from the communityRelease so you
can work today.

--
Jody Garnett

On 23 March 2017 at 18:58, Jody Garnett <jody.garnett@anonymised.com> wrote:

No I changed the jobs to say -PcommunityRelease,!geogig

--
Jody Garnett

On 23 March 2017 at 18:21, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Jody,

do you mean removing geogig from the communityRelease profile?

Kind regards,
Ben.

On 24/03/17 14:09, Jody Garnett wrote:

I am sorry Ben, it does not seem to be a good day for build servers -
the
LocationTech build server was troubled earlier in the day (timing out
when
Erik was trying to reach it).

I am going to go remove geogig from the ares build jobs as a temporary
measure while this is resolved.

--
Jody Garnett

On 23 March 2017 at 17:54, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x)
are
broken because the geogig-master build is failing and has not updated
the
1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the
GeoServer builds to fail. One of these checks had failed and three were
still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the
failing GeoServer Jenkins builds and all the Travis CI branch builds
and
pull request builds that failed because of this outage. I can help with
this step.

Kind regards,

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

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

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

10

Hi,
I’ve previously sent a mail suggesting the geogig plugin to be built with its own dedicated
build on ares, as it’s frequently breaking the builds (compile wise) in GeoServer.
This would also give you the added benefit of being able to run tests on it :slight_smile:

Cheers
Andrea

···

On Fri, Mar 24, 2017 at 1:54 AM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x) are
broken because the geogig-master build is failing and has not updated
the 1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the
GeoServer builds to fail. One of these checks had failed and three were
still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the
failing GeoServer Jenkins builds and all the Travis CI branch builds and
pull request builds that failed because of this outage. I can help with
this step.

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.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

==
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.

11

I have just set that up with Erik for master, if that works as intended we will back port to the other branches.

···

On 24 March 2017 at 00:19, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi,
I’ve previously sent a mail suggesting the geogig plugin to be built with its own dedicated
build on ares, as it’s frequently breaking the builds (compile wise) in GeoServer.
This would also give you the added benefit of being able to run tests on it :slight_smile:

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

–
Jody Garnett

On Fri, Mar 24, 2017 at 1:54 AM, Ben Caradoc-Davies <ben@…4191…> wrote:

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x) are
broken because the geogig-master build is failing and has not updated
the 1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the
GeoServer builds to fail. One of these checks had failed and three were
still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the
failing GeoServer Jenkins builds and all the Travis CI branch builds and
pull request builds that failed because of this outage. I can help with
this step.

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

–

==
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.

12

All, the LocationTech build servers that build the GeoGig core artifacts appear to be functioning again. I’m going to re-trigger the build for this PR:

https://github.com/geoserver/geoserver/pull/2191

Merging this PR will compile the GeoGig module in the Travis build when a GeoServer PR is created, but the GeoGig module will remain disabled in the communityRelease for now. Once merged, GeoGig compilation/build issues may cause GeoServer GitHub Travis builds to fail, but they won’t cause GeoServer builds to fail. If this is an acceptable measure, Jody would you mind merging the PR and backporting. If this is not an acceptable measure, please let me know and I will try to come up with a better solution.

Again, my apologies for the inconveniences caused. When the GeoGig API gets to a less fluid state, we (the GeoGig team) can propose to re-enable the module in the communityRelease.

Many thanks,

···

On Fri, Mar 24, 2017 at 2:25 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

I have just set that up with Erik for master, if that works as intended we will back port to the other branches.

Erik Merkle
Software Engineer | Boundless

–
Jody Garnett

On 24 March 2017 at 00:19, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi,
I’ve previously sent a mail suggesting the geogig plugin to be built with its own dedicated
build on ares, as it’s frequently breaking the builds (compile wise) in GeoServer.
This would also give you the added benefit of being able to run tests on it :slight_smile:

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.comrge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

On Fri, Mar 24, 2017 at 1:54 AM, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x) are
broken because the geogig-master build is failing and has not updated
the 1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the
GeoServer builds to fail. One of these checks had failed and three were
still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the
failing GeoServer Jenkins builds and all the Travis CI branch builds and
pull request builds that failed because of this outage. I can help with
this step.

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

–

==
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.

13

Erik,

I am unhappy with this pull request because it makes Travis CI and ares Jenkins inconsistent. This affects all pull requests. I would rather have the geogig module back in the communityRelease profile and closely monitored by GeoGig developers. The recent failure was caused by an infrastructure problem not an API change (there was an API change but the corresponding fixes were immediately merged into GeoServer). I would rather have the ares build fail for a short time every now and then than break the consistency between Travis CI and ares Jenkins.

Another solution could be to make a stable GeoGig branch for GeoServer to consume and backport GeoGig API changes to this branch at your convenience. This will allow you to choose when to deal with API changes on the GeoServer side. You could achieve the same effect with GeoGig milestones or changing the GeoGig pom version. How much GeoGig API change is coming, and which approach do you think would be easiest?

I have no problem with including the geogig module in the communityRelease profile right now if it compiles and will in the future receive your usual close attention.

Kind regards,
Ben.

On 29/03/17 02:46, Erik Merkle wrote:

All, the LocationTech build servers that build the GeoGig core artifacts
appear to be functioning again. I'm going to re-trigger the build for this
PR:

https://github.com/geoserver/geoserver/pull/2191

Merging this PR will compile the GeoGig module in the Travis build when a
GeoServer PR is created, but the GeoGig module will remain disabled in the
communityRelease for now. Once merged, GeoGig compilation/build issues may
cause GeoServer GitHub Travis builds to fail, but they won't cause
GeoServer builds to fail. If this is an acceptable measure, Jody would you
mind merging the PR and backporting. If this is not an acceptable measure,
please let me know and I will try to come up with a better solution.

Again, my apologies for the inconveniences caused. When the GeoGig API gets
to a less fluid state, we (the GeoGig team) can propose to re-enable the
module in the communityRelease.

Many thanks,

Erik Merkle
Software Engineer | Boundless <http://boundlessgeo.com/&gt;

<http://d32wfbeasdaw38.cloudfront.net/img/Boundless_Logo.png&gt;

On Fri, Mar 24, 2017 at 2:25 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

I have just set that up with Erik for master, if that works as intended we
will back port to the other branches.

--
Jody Garnett

On 24 March 2017 at 00:19, Andrea Aime <andrea.aime@anonymised.com>
wrote:

Hi,
I've previously sent a mail suggesting the geogig plugin to be built with
its own dedicated
build on ares, as it's frequently breaking the builds (compile wise) in
GeoServer.
This would also give you the added benefit of being able to run tests on
it :slight_smile:

Cheers
Andrea

On Fri, Mar 24, 2017 at 1:54 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x) are
broken because the geogig-master build is failing and has not updated
the 1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the
GeoServer builds to fail. One of these checks had failed and three were
still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the
failing GeoServer Jenkins builds and all the Travis CI branch builds and
pull request builds that failed because of this outage. I can help with
this step.

Kind regards,

--
Ben Caradoc-Davies <ben@anonymised.com>
Director
Transient Software Limited <http://transient.nz/&gt;
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--

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 <+39%200584%20962313>
fax: +39 0584 1660272 <+39%200584%20166%200272>
mob: +39 339 8844549 <+39%20339%20884%204549>

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.

-------------------------------------------------------

------------------------------------------------------------
------------------
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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

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

14

I’m with Ben on this - I don’t like the idea of travis and jenkins diverging, Also a +1 on a stable release of geogig going into GeoServer as we had issues on the sprint yesterday due to me not updating snapshots (since I want to use my local geotools build) not getting the latest GeoGig jars.

Ian

···

On 29 March 2017 at 22:45, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Erik,

I am unhappy with this pull request because it makes Travis CI and ares
Jenkins inconsistent. This affects all pull requests. I would rather
have the geogig module back in the communityRelease profile and closely
monitored by GeoGig developers. The recent failure was caused by an
infrastructure problem not an API change (there was an API change but
the corresponding fixes were immediately merged into GeoServer). I would
rather have the ares build fail for a short time every now and then than
break the consistency between Travis CI and ares Jenkins.

Another solution could be to make a stable GeoGig branch for GeoServer
to consume and backport GeoGig API changes to this branch at your
convenience. This will allow you to choose when to deal with API changes
on the GeoServer side. You could achieve the same effect with GeoGig
milestones or changing the GeoGig pom version. How much GeoGig API
change is coming, and which approach do you think would be easiest?

I have no problem with including the geogig module in the
communityRelease profile right now if it compiles and will in the future
receive your usual close attention.

Kind regards,
Ben.

On 29/03/17 02:46, Erik Merkle wrote:

All, the LocationTech build servers that build the GeoGig core artifacts
appear to be functioning again. I’m going to re-trigger the build for this
PR:

https://github.com/geoserver/geoserver/pull/2191

Merging this PR will compile the GeoGig module in the Travis build when a
GeoServer PR is created, but the GeoGig module will remain disabled in the
communityRelease for now. Once merged, GeoGig compilation/build issues may
cause GeoServer GitHub Travis builds to fail, but they won’t cause
GeoServer builds to fail. If this is an acceptable measure, Jody would you
mind merging the PR and backporting. If this is not an acceptable measure,
please let me know and I will try to come up with a better solution.

Again, my apologies for the inconveniences caused. When the GeoGig API gets
to a less fluid state, we (the GeoGig team) can propose to re-enable the
module in the communityRelease.

Many thanks,

Erik Merkle
Software Engineer | Boundless <http://boundlessgeo.com/>

<http://d32wfbeasdaw38.cloudfront.net/img/Boundless_Logo.png>

On Fri, Mar 24, 2017 at 2:25 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

I have just set that up with Erik for master, if that works as intended we
will back port to the other branches.

–
Jody Garnett

On 24 March 2017 at 00:19, Andrea Aime <andrea.aime@anonymised.com>
wrote:

Hi,
I’ve previously sent a mail suggesting the geogig plugin to be built with
its own dedicated
build on ares, as it’s frequently breaking the builds (compile wise) in
GeoServer.
This would also give you the added benefit of being able to run tests on
it :slight_smile:

Cheers
Andrea

On Fri, Mar 24, 2017 at 1:54 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x) are
broken because the geogig-master build is failing and has not updated
the 1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the
GeoServer builds to fail. One of these checks had failed and three were
still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the
failing GeoServer Jenkins builds and all the Travis CI branch builds and
pull request builds that failed because of this outage. I can help with
this step.

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.comsourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

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 <+39%200584%20962313>
fax: +39 0584 1660272 <+39%200584%20166%200272>
mob: +39 339 8844549 <+39%20339%20884%204549>

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.

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.comsourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
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.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Ian Turton

15

Ben, Ian, thanks for the feedback. I agree it would be best to not have different behaviors. I’ll close the PR.

The GeoGig builds appear to be stable again. I’ll monitor them for a few more days to make sure the problem doesn’t pop back up, as LocationTech wasn’t able to identify the cause of the issue (when they investigated, an VM was down that they restarted and were unable to reproduce the issue). If no issues pop up, I’ll submit a new PR to re-enable the GeoGig module in the communityRelease.

Many thanks,

···

On Thu, Mar 30, 2017 at 2:39 AM, Ian Turton <ijturton@anonymised.com> wrote:

I’m with Ben on this - I don’t like the idea of travis and jenkins diverging, Also a +1 on a stable release of geogig going into GeoServer as we had issues on the sprint yesterday due to me not updating snapshots (since I want to use my local geotools build) not getting the latest GeoGig jars.

Ian

Erik Merkle
Software Engineer | Boundless

On 29 March 2017 at 22:45, Ben Caradoc-Davies <ben@anonymised.com> wrote:

Erik,

I am unhappy with this pull request because it makes Travis CI and ares
Jenkins inconsistent. This affects all pull requests. I would rather
have the geogig module back in the communityRelease profile and closely
monitored by GeoGig developers. The recent failure was caused by an
infrastructure problem not an API change (there was an API change but
the corresponding fixes were immediately merged into GeoServer). I would
rather have the ares build fail for a short time every now and then than
break the consistency between Travis CI and ares Jenkins.

Another solution could be to make a stable GeoGig branch for GeoServer
to consume and backport GeoGig API changes to this branch at your
convenience. This will allow you to choose when to deal with API changes
on the GeoServer side. You could achieve the same effect with GeoGig
milestones or changing the GeoGig pom version. How much GeoGig API
change is coming, and which approach do you think would be easiest?

I have no problem with including the geogig module in the
communityRelease profile right now if it compiles and will in the future
receive your usual close attention.

Kind regards,
Ben.

On 29/03/17 02:46, Erik Merkle wrote:

All, the LocationTech build servers that build the GeoGig core artifacts
appear to be functioning again. I’m going to re-trigger the build for this
PR:

https://github.com/geoserver/geoserver/pull/2191

Merging this PR will compile the GeoGig module in the Travis build when a
GeoServer PR is created, but the GeoGig module will remain disabled in the
communityRelease for now. Once merged, GeoGig compilation/build issues may
cause GeoServer GitHub Travis builds to fail, but they won’t cause
GeoServer builds to fail. If this is an acceptable measure, Jody would you
mind merging the PR and backporting. If this is not an acceptable measure,
please let me know and I will try to come up with a better solution.

Again, my apologies for the inconveniences caused. When the GeoGig API gets
to a less fluid state, we (the GeoGig team) can propose to re-enable the
module in the communityRelease.

Many thanks,

Erik Merkle
Software Engineer | Boundless <http://boundlessgeo.com/>

<http://d32wfbeasdaw38.cloudfront.net/img/Boundless_Logo.png>

On Fri, Mar 24, 2017 at 2:25 PM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

I have just set that up with Erik for master, if that works as intended we
will back port to the other branches.

–
Jody Garnett

On 24 March 2017 at 00:19, Andrea Aime <andrea.aime@anonymised.com>
wrote:

Hi,
I’ve previously sent a mail suggesting the geogig plugin to be built with
its own dedicated
build on ares, as it’s frequently breaking the builds (compile wise) in
GeoServer.
This would also give you the added benefit of being able to run tests on
it :slight_smile:

Cheers
Andrea

On Fri, Mar 24, 2017 at 1:54 AM, Ben Caradoc-Davies <ben@anonymised.com>
wrote:

Erik,

GeoServer builds on all branches (master, 2.11.x, 2.10.x, and 2.9.x) are
broken because the geogig-master build is failing and has not updated
the 1.1-SNAPSHOT jars to include the most recent API changes:
https://ci.locationtech.org/geogig/job/geogig-master/

Travis CI correctly identified that these pull requests would cause the
GeoServer builds to fail. One of these checks had failed and three were
still pending at the time that you merged these pull requests:
https://github.com/geoserver/geoserver/pull/2183
https://github.com/geoserver/geoserver/pull/2186
https://github.com/geoserver/geoserver/pull/2185
https://github.com/geoserver/geoserver/pull/2184

Once the geogig-master build has been fixed, please restart all the
failing GeoServer Jenkins builds and all the Travis CI branch builds and
pull request builds that failed because of this outage. I can help with
this step.

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

–

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 <+39%200584%20962313>
fax: +39 0584 1660272 <+39%200584%20166%200272>
mob: +39 339 8844549 <+39%20339%20884%204549>

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.

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

–
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

–

Ian Turton

16

Ian,

this sounds like the problem I see because I always build with "mvn -nsu" to ensure that I use artifacts from my local geotools build. Because geoscript and geogig are two snapshot dependencies that I do not build locally, the script I use to compile community modules starts with this:

# manually remove external snapshot dependencies
rm -rf ~/.m2/repository/org/geoscript
rm -rf ~/.m2/repository/org/locationtech/geogig

Crude, but effective.

Kind regards,
Ben.

On 30/03/17 20:39, Ian Turton wrote:

I'm with Ben on this - I don't like the idea of travis and jenkins
diverging, Also a +1 on a stable release of geogig going into GeoServer as
we had issues on the sprint yesterday due to me not updating snapshots
(since I want to use my local geotools build) not getting the latest GeoGig
jars.

Ian

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