[Geoserver-devel] 18.x 2.12.x release blocked

As I said in another message the cite-tests currently don’t run on the new build server. I just tried to run the cite tests on ares but that won’t work as there is no geoserver-12.x build configured. I’m loathe to set up a complete 2.12.x build on ares as we are trying to move away from it and I’m not sure what the possible interactions are.

So if someone with a fixed IP address can fix the new build server up that would be great as currently all the cite tests currently claim to be passing but are in fact failing.

cheers

Ian

···

Ian Turton

Hi Ian,

It looks like the cite tests on the new build server still need a bit more work before they are functional; Jody, Nick, Justin, and Ben seem to be arranging something to look into that; but that probably won’t be in time for the release.

Given that, best bet is probably to use ares. I was hoping we could avoid creating the 2.12 jobs on ares as well, but I guess that is not going to be the case. I’ve created a 2.12.x nightly on ares, and kicked off another batch of cite tests.

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Torben

···

On Fri, Oct 6, 2017 at 3:32 AM, Ian Turton <ijturton@anonymised.com> wrote:

As I said in another message the cite-tests currently don’t run on the new build server. I just tried to run the cite tests on ares but that won’t work as there is no geoserver-12.x build configured. I’m loathe to set up a complete 2.12.x build on ares as we are trying to move away from it and I’m not sure what the possible interactions are.

So if someone with a fixed IP address can fix the new build server up that would be great as currently all the cite tests currently claim to be passing but are in fact failing.

cheers

Ian

Ian Turton


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.com66…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Can we run cite tests on ares to verify the revision numbers, and then make the release on build.geoserver.org ?

···

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hi Ian,

It looks like the cite tests on the new build server still need a bit more work before they are functional; Jody, Nick, Justin, and Ben seem to be arranging something to look into that; but that probably won’t be in time for the release.

Given that, best bet is probably to use ares. I was hoping we could avoid creating the 2.12 jobs on ares as well, but I guess that is not going to be the case. I’ve created a 2.12.x nightly on ares, and kicked off another batch of cite tests.

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Torben


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.com66…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel


Jody Garnett

On Fri, Oct 6, 2017 at 3:32 AM, Ian Turton <ijturton@anonymised.com> wrote:

As I said in another message the cite-tests currently don’t run on the new build server. I just tried to run the cite tests on ares but that won’t work as there is no geoserver-12.x build configured. I’m loathe to set up a complete 2.12.x build on ares as we are trying to move away from it and I’m not sure what the possible interactions are.

So if someone with a fixed IP address can fix the new build server up that would be great as currently all the cite tests currently claim to be passing but are in fact failing.

cheers

Ian

Ian Turton


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.com>
wrote:

Running the cite tests on ares and the build on the new build server works
fine, from past experience.

On Fri, Oct 6, 2017 at 9:23 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Can we run cite tests on ares to verify the revision numbers, and then
make the release on build.geoserver.org ?

Yes

Torben

--
Jody Garnett

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.com>
wrote:

Hi Ian,

It looks like the cite tests on the new build server still need a bit
more work before they are functional; Jody, Nick, Justin, and Ben seem to
be arranging something to look into that; but that probably won't be in
time for the release.

Given that, best bet is probably to use ares. I was hoping we could avoid
creating the 2.12 jobs on ares as well, but I guess that is not going to be
the case. I've created a 2.12.x nightly on ares, and kicked off another
batch of cite tests.

Running the cite tests on ares and the build on the new build server
works fine, from past experience.

Torben

On Fri, Oct 6, 2017 at 3:32 AM, Ian Turton <ijturton@anonymised.com> wrote:

As I said in another message the cite-tests currently don't run on the
new build server. I just tried to run the cite tests on ares but that won't
work as there is no geoserver-12.x build configured. I'm loathe to set up a
complete 2.12.x build on ares as we are trying to move away from it and I'm
not sure what the possible interactions are.

So if someone with a fixed IP address can fix the new build server up
that would be great as currently all the cite tests currently claim to be
passing but are in fact failing.

cheers

Ian

--
Ian Turton

------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
geotools-devel List Signup and Options

------------------------------------------------------------
------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
geotools-devel List Signup and Options

Thanks Torben

I think all the cite tests on the new build server need is one jar installed

Cheers

Ian

···

On 6 October 2017 at 17:27, Torben Barsballe <tbarsballe@anonymised.com> wrote:

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@boundlessgeo.com> wrote:

Running the cite tests on ares and the build on the new build server works fine, from past experience.

On Fri, Oct 6, 2017 at 9:23 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Can we run cite tests on ares to verify the revision numbers, and then make the release on build.geoserver.org ?

Yes

Torben


Jody Garnett

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hi Ian,

It looks like the cite tests on the new build server still need a bit more work before they are functional; Jody, Nick, Justin, and Ben seem to be arranging something to look into that; but that probably won’t be in time for the release.

Given that, best bet is probably to use ares. I was hoping we could avoid creating the 2.12 jobs on ares as well, but I guess that is not going to be the case. I’ve created a 2.12.x nightly on ares, and kicked off another batch of cite tests.

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Torben


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

On Fri, Oct 6, 2017 at 3:32 AM, Ian Turton <ijturton@anonymised.com> wrote:

As I said in another message the cite-tests currently don’t run on the new build server. I just tried to run the cite tests on ares but that won’t work as there is no geoserver-12.x build configured. I’m loathe to set up a complete 2.12.x build on ares as we are trying to move away from it and I’m not sure what the possible interactions are.

So if someone with a fixed IP address can fix the new build server up that would be great as currently all the cite tests currently claim to be passing but are in fact failing.

cheers

Ian

Ian Turton


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Ian Turton

It was not my intension to hold up the relesae by asking for a team to port cite jobs, goal is to shut of ares.

Here are the revisions from ares: http://ares.boundlessgeo.com/jenkins/view/testing-cite/job/2.12-cite-wfs-1.0/lastSuccessfulBuild/

version = 2.12-SNAPSHOT
git revision = bc18e09993a30c93f37b7e33e7c54c32b17e014b
git branch = origin/2.12.x
build date = 06-Oct-2017 15:52
geotools version = 18-SNAPSHOT
geotools revision = 3f5dbf634c4a6b24476643cc7cf7d2b22747fcf5
geowebcache version = 1.12-SNAPSHOT
geowebcache revision = 5b516f3adc0f82e42f342ba83b5fc9a353d575d2/5b516
hudson build = -1

Not sure if we should trust this without doing a nightly build on ares, and then the cite tests.

···

On 6 October 2017 at 09:27, Torben Barsballe <tbarsballe@anonymised.com> wrote:

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@boundlessgeo.com> wrote:

Running the cite tests on ares and the build on the new build server works fine, from past experience.


Jody Garnett

On Fri, Oct 6, 2017 at 9:23 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Can we run cite tests on ares to verify the revision numbers, and then make the release on build.geoserver.org ?

Yes

Torben


Jody Garnett

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hi Ian,

It looks like the cite tests on the new build server still need a bit more work before they are functional; Jody, Nick, Justin, and Ben seem to be arranging something to look into that; but that probably won’t be in time for the release.

Given that, best bet is probably to use ares. I was hoping we could avoid creating the 2.12 jobs on ares as well, but I guess that is not going to be the case. I’ve created a 2.12.x nightly on ares, and kicked off another batch of cite tests.

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Torben


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

On Fri, Oct 6, 2017 at 3:32 AM, Ian Turton <ijturton@anonymised.com> wrote:

As I said in another message the cite-tests currently don’t run on the new build server. I just tried to run the cite tests on ares but that won’t work as there is no geoserver-12.x build configured. I’m loathe to set up a complete 2.12.x build on ares as we are trying to move away from it and I’m not sure what the possible interactions are.

So if someone with a fixed IP address can fix the new build server up that would be great as currently all the cite tests currently claim to be passing but are in fact failing.

cheers

Ian

Ian Turton


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Jody - I created, and ran a nightly build on ares about an hour ago; thats the only reason the cite tests are actually passing on ares right now (althought they are still in progress, all seem to be passing so far).

···

On Fri, Oct 6, 2017 at 9:44 AM, Jody Garnett <jody.garnett@anonymised.com.> wrote:

It was not my intension to hold up the relesae by asking for a team to port cite jobs, goal is to shut of ares.

Here are the revisions from ares: http://ares.boundlessgeo.com/jenkins/view/testing-cite/job/2.12-cite-wfs-1.0/lastSuccessfulBuild/

version = 2.12-SNAPSHOT
git revision = bc18e09993a30c93f37b7e33e7c54c32b17e014b
git branch = origin/2.12.x
build date = 06-Oct-2017 15:52
geotools version = 18-SNAPSHOT
geotools revision = 3f5dbf634c4a6b24476643cc7cf7d2b22747fcf5
geowebcache version = 1.12-SNAPSHOT
geowebcache revision = 5b516f3adc0f82e42f342ba83b5fc9a353d575d2/5b516
hudson build = -1

Not sure if we should trust this without doing a nightly build on ares, and then the cite tests.


Jody Garnett

On 6 October 2017 at 09:27, Torben Barsballe <tbarsballe@anonymised.com> wrote:

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.comsgeo.com> wrote:

Running the cite tests on ares and the build on the new build server works fine, from past experience.

On Fri, Oct 6, 2017 at 9:23 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Can we run cite tests on ares to verify the revision numbers, and then make the release on build.geoserver.org ?

Yes

Torben


Jody Garnett

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hi Ian,

It looks like the cite tests on the new build server still need a bit more work before they are functional; Jody, Nick, Justin, and Ben seem to be arranging something to look into that; but that probably won’t be in time for the release.

Given that, best bet is probably to use ares. I was hoping we could avoid creating the 2.12 jobs on ares as well, but I guess that is not going to be the case. I’ve created a 2.12.x nightly on ares, and kicked off another batch of cite tests.

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Torben


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

On Fri, Oct 6, 2017 at 3:32 AM, Ian Turton <ijturton@anonymised.com> wrote:

As I said in another message the cite-tests currently don’t run on the new build server. I just tried to run the cite tests on ares but that won’t work as there is no geoserver-12.x build configured. I’m loathe to set up a complete 2.12.x build on ares as we are trying to move away from it and I’m not sure what the possible interactions are.

So if someone with a fixed IP address can fix the new build server up that would be great as currently all the cite tests currently claim to be passing but are in fact failing.

cheers

Ian

Ian Turton


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Ian

Looking at the 2.11 cite tests on the new build server, they are failing (although reporting success) for a different reason than the jar (curl: (7) Failed to connect to localhost port 11010 - looks like an issue starting up geoserver or the cite server). So I expect once we get the jar for the 2.12.x cite tests, they will just be failing in a different way. It seems like each time one of the cite test issues get fixed, there is another one underneath.

Torben

···

On Fri, Oct 6, 2017 at 9:42 AM, Ian Turton <ijturton@anonymised.com> wrote:

Thanks Torben

I think all the cite tests on the new build server need is one jar installed

Cheers

Ian

On 6 October 2017 at 17:27, Torben Barsballe <tbarsballe@anonymised.com3839…> wrote:

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.comsgeo.com> wrote:

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Ian Turton

On Fri, Oct 6, 2017 at 9:23 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Can we run cite tests on ares to verify the revision numbers, and then make the release on build.geoserver.org ?

Yes

Torben


Jody Garnett

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hi Ian,

It looks like the cite tests on the new build server still need a bit more work before they are functional; Jody, Nick, Justin, and Ben seem to be arranging something to look into that; but that probably won’t be in time for the release.

Given that, best bet is probably to use ares. I was hoping we could avoid creating the 2.12 jobs on ares as well, but I guess that is not going to be the case. I’ve created a 2.12.x nightly on ares, and kicked off another batch of cite tests.

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Torben


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

On Fri, Oct 6, 2017 at 3:32 AM, Ian Turton <ijturton@anonymised.com> wrote:

As I said in another message the cite-tests currently don’t run on the new build server. I just tried to run the cite tests on ares but that won’t work as there is no geoserver-12.x build configured. I’m loathe to set up a complete 2.12.x build on ares as we are trying to move away from it and I’m not sure what the possible interactions are.

So if someone with a fixed IP address can fix the new build server up that would be great as currently all the cite tests currently claim to be passing but are in fact failing.

cheers

Ian

Ian Turton


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

All 2.12.x cite tests now passing on ares. Jody posted the revision info above, but here it is again:

version = 2.12-SNAPSHOT
git revision = bc18e09993a30c93f37b7e33e7c54c32b17e014b
git branch = origin/2.12.x
build date = 06-Oct-2017 15:52
geotools version = 18-SNAPSHOT
geotools revision = 3f5dbf634c4a6b24476643cc7cf7d2b22747fcf5
geowebcache version = 1.12-SNAPSHOT
geowebcache revision = 5b516f3adc0f82e42f342ba83b5fc9a353d575d2/5b516

Torben

···

On Fri, Oct 6, 2017 at 9:52 AM, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Ian

Looking at the 2.11 cite tests on the new build server, they are failing (although reporting success) for a different reason than the jar (curl: (7) Failed to connect to localhost port 11010 - looks like an issue starting up geoserver or the cite server). So I expect once we get the jar for the 2.12.x cite tests, they will just be failing in a different way. It seems like each time one of the cite test issues get fixed, there is another one underneath.

Torben

On Fri, Oct 6, 2017 at 9:42 AM, Ian Turton <ijturton@anonymised.com> wrote:

Thanks Torben

I think all the cite tests on the new build server need is one jar installed

Cheers

Ian

On 6 October 2017 at 17:27, Torben Barsballe <tbarsballe@anonymised.com> wrote:

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.comsgeo.com> wrote:

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Ian Turton

On Fri, Oct 6, 2017 at 9:23 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Can we run cite tests on ares to verify the revision numbers, and then make the release on build.geoserver.org ?

Yes

Torben


Jody Garnett

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hi Ian,

It looks like the cite tests on the new build server still need a bit more work before they are functional; Jody, Nick, Justin, and Ben seem to be arranging something to look into that; but that probably won’t be in time for the release.

Given that, best bet is probably to use ares. I was hoping we could avoid creating the 2.12 jobs on ares as well, but I guess that is not going to be the case. I’ve created a 2.12.x nightly on ares, and kicked off another batch of cite tests.

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Torben


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

On Fri, Oct 6, 2017 at 3:32 AM, Ian Turton <ijturton@anonymised.com> wrote:

As I said in another message the cite-tests currently don’t run on the new build server. I just tried to run the cite tests on ares but that won’t work as there is no geoserver-12.x build configured. I’m loathe to set up a complete 2.12.x build on ares as we are trying to move away from it and I’m not sure what the possible interactions are.

So if someone with a fixed IP address can fix the new build server up that would be great as currently all the cite tests currently claim to be passing but are in fact failing.

cheers

Ian

Ian Turton


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

OK I’ve pushed the release job on new build (we should name that machine) - I’ll see how it goes

Ian

···

On 6 October 2017 at 17:54, Torben Barsballe <tbarsballe@anonymised.com> wrote:

All 2.12.x cite tests now passing on ares. Jody posted the revision info above, but here it is again:

version = 2.12-SNAPSHOT
git revision = bc18e09993a30c93f37b7e33e7c54c32b17e014b
git branch = origin/2.12.x
build date = 06-Oct-2017 15:52
geotools version = 18-SNAPSHOT
geotools revision = 3f5dbf634c4a6b24476643cc7cf7d2b22747fcf5
geowebcache version = 1.12-SNAPSHOT
geowebcache revision = 5b516f3adc0f82e42f342ba83b5fc9a353d575d2/5b516

Torben

On Fri, Oct 6, 2017 at 9:52 AM, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Ian

Looking at the 2.11 cite tests on the new build server, they are failing (although reporting success) for a different reason than the jar (curl: (7) Failed to connect to localhost port 11010 - looks like an issue starting up geoserver or the cite server). So I expect once we get the jar for the 2.12.x cite tests, they will just be failing in a different way. It seems like each time one of the cite test issues get fixed, there is another one underneath.

Torben

On Fri, Oct 6, 2017 at 9:42 AM, Ian Turton <ijturton@anonymised.com> wrote:

Thanks Torben

I think all the cite tests on the new build server need is one jar installed

Cheers

Ian

On 6 October 2017 at 17:27, Torben Barsballe <tbarsballe@anonymised.com> wrote:

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.comsgeo.com> wrote:

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Ian Turton

On Fri, Oct 6, 2017 at 9:23 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Can we run cite tests on ares to verify the revision numbers, and then make the release on build.geoserver.org ?

Yes

Torben


Jody Garnett

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hi Ian,

It looks like the cite tests on the new build server still need a bit more work before they are functional; Jody, Nick, Justin, and Ben seem to be arranging something to look into that; but that probably won’t be in time for the release.

Given that, best bet is probably to use ares. I was hoping we could avoid creating the 2.12 jobs on ares as well, but I guess that is not going to be the case. I’ve created a 2.12.x nightly on ares, and kicked off another batch of cite tests.

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Torben


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

On Fri, Oct 6, 2017 at 3:32 AM, Ian Turton <ijturton@anonymised.com> wrote:

As I said in another message the cite-tests currently don’t run on the new build server. I just tried to run the cite tests on ares but that won’t work as there is no geoserver-12.x build configured. I’m loathe to set up a complete 2.12.x build on ares as we are trying to move away from it and I’m not sure what the possible interactions are.

So if someone with a fixed IP address can fix the new build server up that would be great as currently all the cite tests currently claim to be passing but are in fact failing.

cheers

Ian

Ian Turton


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Ian Turton

Excellent.

I believe it is named apollo internally. We just need to start using the name, so that everyone knows what we are talking about when someone says “apollo”.

Torben

···

On Fri, Oct 6, 2017 at 9:55 AM, Ian Turton <ijturton@anonymised.com…> wrote:

OK I’ve pushed the release job on new build (we should name that machine) - I’ll see how it goes

Ian

On 6 October 2017 at 17:54, Torben Barsballe <tbarsballe@anonymised.com> wrote:

All 2.12.x cite tests now passing on ares. Jody posted the revision info above, but here it is again:

version = 2.12-SNAPSHOT
git revision = bc18e09993a30c93f37b7e33e7c54c32b17e014b
git branch = origin/2.12.x
build date = 06-Oct-2017 15:52
geotools version = 18-SNAPSHOT
geotools revision = 3f5dbf634c4a6b24476643cc7cf7d2b22747fcf5
geowebcache version = 1.12-SNAPSHOT
geowebcache revision = 5b516f3adc0f82e42f342ba83b5fc9a353d575d2/5b516

Torben

Ian Turton

On Fri, Oct 6, 2017 at 9:52 AM, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Ian

Looking at the 2.11 cite tests on the new build server, they are failing (although reporting success) for a different reason than the jar (curl: (7) Failed to connect to localhost port 11010 - looks like an issue starting up geoserver or the cite server). So I expect once we get the jar for the 2.12.x cite tests, they will just be failing in a different way. It seems like each time one of the cite test issues get fixed, there is another one underneath.

Torben

On Fri, Oct 6, 2017 at 9:42 AM, Ian Turton <ijturton@anonymised.com> wrote:

Thanks Torben

I think all the cite tests on the new build server need is one jar installed

Cheers

Ian

On 6 October 2017 at 17:27, Torben Barsballe <tbarsballe@anonymised.com> wrote:

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.comsgeo.com> wrote:

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Ian Turton

On Fri, Oct 6, 2017 at 9:23 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Can we run cite tests on ares to verify the revision numbers, and then make the release on build.geoserver.org ?

Yes

Torben


Jody Garnett

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hi Ian,

It looks like the cite tests on the new build server still need a bit more work before they are functional; Jody, Nick, Justin, and Ben seem to be arranging something to look into that; but that probably won’t be in time for the release.

Given that, best bet is probably to use ares. I was hoping we could avoid creating the 2.12 jobs on ares as well, but I guess that is not going to be the case. I’ve created a 2.12.x nightly on ares, and kicked off another batch of cite tests.

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Torben


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

On Fri, Oct 6, 2017 at 3:32 AM, Ian Turton <ijturton@anonymised.com> wrote:

As I said in another message the cite-tests currently don’t run on the new build server. I just tried to run the cite tests on ares but that won’t work as there is no geoserver-12.x build configured. I’m loathe to set up a complete 2.12.x build on ares as we are trying to move away from it and I’m not sure what the possible interactions are.

So if someone with a fixed IP address can fix the new build server up that would be great as currently all the cite tests currently claim to be passing but are in fact failing.

cheers

Ian

Ian Turton


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

I thought it was named “build” :slight_smile:

···

On 6 October 2017 at 10:02, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Excellent.

I believe it is named apollo internally. We just need to start using the name, so that everyone knows what we are talking about when someone says “apollo”.

Torben


Jody Garnett

On Fri, Oct 6, 2017 at 9:55 AM, Ian Turton <ijturton@anonymised.com> wrote:

OK I’ve pushed the release job on new build (we should name that machine) - I’ll see how it goes

Ian

On 6 October 2017 at 17:54, Torben Barsballe <tbarsballe@anonymised.com> wrote:

All 2.12.x cite tests now passing on ares. Jody posted the revision info above, but here it is again:

version = 2.12-SNAPSHOT
git revision = bc18e09993a30c93f37b7e33e7c54c32b17e014b
git branch = origin/2.12.x
build date = 06-Oct-2017 15:52
geotools version = 18-SNAPSHOT
geotools revision = 3f5dbf634c4a6b24476643cc7cf7d2b22747fcf5
geowebcache version = 1.12-SNAPSHOT
geowebcache revision = 5b516f3adc0f82e42f342ba83b5fc9a353d575d2/5b516

Torben

Ian Turton

On Fri, Oct 6, 2017 at 9:52 AM, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Ian

Looking at the 2.11 cite tests on the new build server, they are failing (although reporting success) for a different reason than the jar (curl: (7) Failed to connect to localhost port 11010 - looks like an issue starting up geoserver or the cite server). So I expect once we get the jar for the 2.12.x cite tests, they will just be failing in a different way. It seems like each time one of the cite test issues get fixed, there is another one underneath.

Torben

On Fri, Oct 6, 2017 at 9:42 AM, Ian Turton <ijturton@anonymised.com> wrote:

Thanks Torben

I think all the cite tests on the new build server need is one jar installed

Cheers

Ian

On 6 October 2017 at 17:27, Torben Barsballe <tbarsballe@anonymised.com> wrote:

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.comsgeo.com> wrote:

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Ian Turton

On Fri, Oct 6, 2017 at 9:23 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Can we run cite tests on ares to verify the revision numbers, and then make the release on build.geoserver.org ?

Yes

Torben


Jody Garnett

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hi Ian,

It looks like the cite tests on the new build server still need a bit more work before they are functional; Jody, Nick, Justin, and Ben seem to be arranging something to look into that; but that probably won’t be in time for the release.

Given that, best bet is probably to use ares. I was hoping we could avoid creating the 2.12 jobs on ares as well, but I guess that is not going to be the case. I’ve created a 2.12.x nightly on ares, and kicked off another batch of cite tests.

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Torben


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

On Fri, Oct 6, 2017 at 3:32 AM, Ian Turton <ijturton@anonymised.com> wrote:

As I said in another message the cite-tests currently don’t run on the new build server. I just tried to run the cite tests on ares but that won’t work as there is no geoserver-12.x build configured. I’m loathe to set up a complete 2.12.x build on ares as we are trying to move away from it and I’m not sure what the possible interactions are.

So if someone with a fixed IP address can fix the new build server up that would be great as currently all the cite tests currently claim to be passing but are in fact failing.

cheers

Ian

Ian Turton


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

If you look at the executors, they are all named apollo; the URL is just build :wink:

···

On Fri, Oct 6, 2017 at 11:57 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

I thought it was named “build” :slight_smile:


Jody Garnett

On 6 October 2017 at 10:02, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Excellent.

I believe it is named apollo internally. We just need to start using the name, so that everyone knows what we are talking about when someone says “apollo”.

Torben

On Fri, Oct 6, 2017 at 9:55 AM, Ian Turton <ijturton@anonymised.com> wrote:

OK I’ve pushed the release job on new build (we should name that machine) - I’ll see how it goes

Ian

On 6 October 2017 at 17:54, Torben Barsballe <tbarsballe@anonymised.com> wrote:

All 2.12.x cite tests now passing on ares. Jody posted the revision info above, but here it is again:

version = 2.12-SNAPSHOT
git revision = bc18e09993a30c93f37b7e33e7c54c32b17e014b
git branch = origin/2.12.x
build date = 06-Oct-2017 15:52
geotools version = 18-SNAPSHOT
geotools revision = 3f5dbf634c4a6b24476643cc7cf7d2b22747fcf5
geowebcache version = 1.12-SNAPSHOT
geowebcache revision = 5b516f3adc0f82e42f342ba83b5fc9a353d575d2/5b516

Torben

Ian Turton

On Fri, Oct 6, 2017 at 9:52 AM, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Ian

Looking at the 2.11 cite tests on the new build server, they are failing (although reporting success) for a different reason than the jar (curl: (7) Failed to connect to localhost port 11010 - looks like an issue starting up geoserver or the cite server). So I expect once we get the jar for the 2.12.x cite tests, they will just be failing in a different way. It seems like each time one of the cite test issues get fixed, there is another one underneath.

Torben

On Fri, Oct 6, 2017 at 9:42 AM, Ian Turton <ijturton@anonymised.com> wrote:

Thanks Torben

I think all the cite tests on the new build server need is one jar installed

Cheers

Ian

On 6 October 2017 at 17:27, Torben Barsballe <tbarsballe@anonymised.com> wrote:

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.comsgeo.com> wrote:

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Ian Turton

On Fri, Oct 6, 2017 at 9:23 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Can we run cite tests on ares to verify the revision numbers, and then make the release on build.geoserver.org ?

Yes

Torben


Jody Garnett

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hi Ian,

It looks like the cite tests on the new build server still need a bit more work before they are functional; Jody, Nick, Justin, and Ben seem to be arranging something to look into that; but that probably won’t be in time for the release.

Given that, best bet is probably to use ares. I was hoping we could avoid creating the 2.12 jobs on ares as well, but I guess that is not going to be the case. I’ve created a 2.12.x nightly on ares, and kicked off another batch of cite tests.

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Torben


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

On Fri, Oct 6, 2017 at 3:32 AM, Ian Turton <ijturton@anonymised.com.403…> wrote:

As I said in another message the cite-tests currently don’t run on the new build server. I just tried to run the cite tests on ares but that won’t work as there is no geoserver-12.x build configured. I’m loathe to set up a complete 2.12.x build on ares as we are trying to move away from it and I’m not sure what the possible interactions are.

So if someone with a fixed IP address can fix the new build server up that would be great as currently all the cite tests currently claim to be passing but are in fact failing.

cheers

Ian

Ian Turton


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Most of JARs of 2.12.x are old. Some mess around with artifacts I’m afraid.

(attachments)

image.png

···

On Fri, Oct 6, 2017 at 9:09 PM, Torben Barsballe <tbarsballe@anonymised.com> wrote:

If you look at the executors, they are all named apollo; the URL is just build :wink:

Inline image 1


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.com66…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Regards,

Alessio Fabiani

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

Ing. Alessio Fabiani

@alfa7691
Founder/Technical Lead

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

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.

On Fri, Oct 6, 2017 at 11:57 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

I thought it was named “build” :slight_smile:


Jody Garnett

On 6 October 2017 at 10:02, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Excellent.

I believe it is named apollo internally. We just need to start using the name, so that everyone knows what we are talking about when someone says “apollo”.

Torben

On Fri, Oct 6, 2017 at 9:55 AM, Ian Turton <ijturton@anonymised.com> wrote:

OK I’ve pushed the release job on new build (we should name that machine) - I’ll see how it goes

Ian

On 6 October 2017 at 17:54, Torben Barsballe <tbarsballe@anonymised.com> wrote:

All 2.12.x cite tests now passing on ares. Jody posted the revision info above, but here it is again:

version = 2.12-SNAPSHOT
git revision = bc18e09993a30c93f37b7e33e7c54c32b17e014b
git branch = origin/2.12.x
build date = 06-Oct-2017 15:52
geotools version = 18-SNAPSHOT
geotools revision = 3f5dbf634c4a6b24476643cc7cf7d2b22747fcf5
geowebcache version = 1.12-SNAPSHOT
geowebcache revision = 5b516f3adc0f82e42f342ba83b5fc9a353d575d2/5b516

Torben

Ian Turton

On Fri, Oct 6, 2017 at 9:52 AM, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Ian

Looking at the 2.11 cite tests on the new build server, they are failing (although reporting success) for a different reason than the jar (curl: (7) Failed to connect to localhost port 11010 - looks like an issue starting up geoserver or the cite server). So I expect once we get the jar for the 2.12.x cite tests, they will just be failing in a different way. It seems like each time one of the cite test issues get fixed, there is another one underneath.

Torben

On Fri, Oct 6, 2017 at 9:42 AM, Ian Turton <ijturton@anonymised.com> wrote:

Thanks Torben

I think all the cite tests on the new build server need is one jar installed

Cheers

Ian

On 6 October 2017 at 17:27, Torben Barsballe <tbarsballe@anonymised.com> wrote:

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.comsgeo.com> wrote:

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Ian Turton

On Fri, Oct 6, 2017 at 9:23 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Can we run cite tests on ares to verify the revision numbers, and then make the release on build.geoserver.org ?

Yes

Torben


Jody Garnett

On 6 October 2017 at 09:00, Torben Barsballe <tbarsballe@anonymised.com> wrote:

Hi Ian,

It looks like the cite tests on the new build server still need a bit more work before they are functional; Jody, Nick, Justin, and Ben seem to be arranging something to look into that; but that probably won’t be in time for the release.

Given that, best bet is probably to use ares. I was hoping we could avoid creating the 2.12 jobs on ares as well, but I guess that is not going to be the case. I’ve created a 2.12.x nightly on ares, and kicked off another batch of cite tests.

Running the cite tests on ares and the build on the new build server works fine, from past experience.

Torben


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

On Fri, Oct 6, 2017 at 3:32 AM, Ian Turton <ijturton@anonymised.com> wrote:

As I said in another message the cite-tests currently don’t run on the new build server. I just tried to run the cite tests on ares but that won’t work as there is no geoserver-12.x build configured. I’m loathe to set up a complete 2.12.x build on ares as we are trying to move away from it and I’m not sure what the possible interactions are.

So if someone with a fixed IP address can fix the new build server up that would be great as currently all the cite tests currently claim to be passing but are in fact failing.

cheers

Ian

Ian Turton


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


GeoTools-Devel mailing list
GeoTools-Devel@anonymised.comge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel