[Geoserver-devel] GSIP-176 Cite Automation update?

GeoServer GeoServer Developer
1

Simone:

Next week’s Feb 18th meeting is our final meeting in February, is there any update from the Cite Automation work?

With the recent news from Planet Federal I am concerned about ability to deliver into build.geoserver.org environment.

···

–
Jody Garnett

2

Hi Jody,
We are a little beyond schedule with this, the work has started but there is little to show.

We will send periodic updates to the psc and devel list starting next week.

Regards,
Simone Giannecchini

···

Regards,
Simone Giannecchini.
GeoSolutions Director

  • sent from my mobile, apologies for brevity and typos-
3

Thanks, we may need to circle around build.geoserver.org plans.

···

–
Jody Garnett

4

Dear Jody, All

Just a quick update on this:
I set up a test build on the build server for one of the CITE tests to build and deploy the artifacts on the maven repository and
I am currently working on the the docker images and writing the docker-compose file to run the geoserver, postgres and teamengine
containers to execute the tests.
The build job is taking the Github branch and tags as parameters (with defaults) and is not tightly bound to the build environment so It
would be pretty straightforward to migrate it to another build server.
For the docker images and I don’t have something ready to show yet, I’ll let you know as soon as I do.

···

Regards,

Alessandro Parma

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

Alessandro Parma
DevOps Engineer

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

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

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

5

HI Jody, All,

Status update with a couple of questions about the source code management and deployment of this work:

I added more builds for the ets suites, updated list:

  • wms11

  • wms13

  • wfs10

  • wfs11

  • wcs10

  • wcs11

  • wcs20

  • wfs20

Then created a build for the teamengine-docker fork to build the docker image for teamengine with the suites and tools that we need.
The docker image includes all of the sutes that we use and a single docker images can be used by all cite test runs (there is
nothing test-specific in it). This build is currently hosted on this build server because I had some issues with the build on geoserver
build server that I still need to address… The docker image is currently pushed here on the docker hub (more on this later)

I then created a parameterized build to run the tests. It is currently building from my GeoServer fork where I pushed the docker-compose files
and the other auxiliary files required to run the tests. My idea, and I’d like to have feedback from you as well as from the GeoServer
ML, is to add all the files required into the ‘build’ subdirectory of the repository. Would this be ok?
The file structure mimics that in our proposal where we have a global docker-compose.yml file with a ‘geoserver’ and '‘teamengine’ service
definition and subdirectory for every test suite with test specific files like “forms” for command line execution of a given test suite and a
docker-compose override file to spin up postgresql if required by the specific test. For data directories I’d use the ones that are
already available in the repository.

An example execution of this parametrized build is available here where I ran the WMS 1.1.1 suite against the latest geoserver master nightly.

The log files from the test run are stored as artifacts from the job run. There is still some work to do, notably, the job does not fail when a given
test fails (apparently due to the test.sh script in the teamengine suite swallowing the status of the tests. I still need to figure this out) and to add
more builds for the other suites. I’ll keep you informed on my progress on this.

Concerning the docker image(s) for teamengine-docker is there an official repository for GeoServer on the docker hub where I can push the image?

Thank you in advance for your feedback,
Alessandro

···

Regards,

Alessandro Parma

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

Alessandro Parma
DevOps Engineer

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

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

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

6

Thank you for the update!

I think managing the docker builds in the “build” directory is appropriate. Is it worth co-locating these with their cite data directory configuration (to make each folder more self contained)?

aside: In the past when faced with builds grabbing status codes we would grep through the output for failure, not sure how stable that is.

There is not an official repository on docker hub for this, we should set this up (I am not sure what is needed).

···

–
Jody Garnett

7

Thanks for your feedback

My answers inline below

I think managing the docker builds in the “build” directory is appropriate. Is it worth co-locating these with their cite data directory configuration (to make each folder more self contained)?

I agree. I would move the datadirs everything in the build/cite dir along with the docker related file, ok?

aside: In the past when faced with builds grabbing status codes we would grep through the output for failure, not sure how stable that is.

Ok, thank you. I’ll dig a little deeper into to try to avoid grepping the logs, if possible.

There is not an official repository on docker hub for this, we should set this up (I am not sure what is needed).

I think we should create an Organization and a team with members allowed to push the docker image to the hub.

···

Regards,

Alessandro Parma

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

Alessandro Parma
DevOps Engineer

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

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

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

8

Seems like a good idea.

Cheers
Andrea

···

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 ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

9

For repo, would having an osgeo nexus repo help as a place to store the docker images?

···

–
Jody Garnett

10

Alessandro:

We now have repo.osgeo.org operational, the builds should hopefully switch over in the next couple of days.

I have created https://repo.osgeo.org/repository/geoserver-docker/ for you to try out.

···

–
Jody Garnett

11

Dear Jody,
I’m working on setting up the CITE tests automation.

Here is a brief update on the current status:

  • The required “ets-*” artifacts are being built on Jenkins. The deploy phase is currently missing, but it is not blocking as we only have a single server at the moment.

  • The teamengine-docker image is being built on Jenkins.

  • The cite-tests is now working on Jenkins and a first test shows that the cite tests are able to run against the latest GeoServer master.

  • I did a small improvement on the bash scripts to manage the exit code but I think a change in the teamengine-core java code will be needed to properly address this

I’ll continue next week with:

  • Completing the deploy of all the artifacts and docker images in maven repo and dockehub

  • Improve the readability of the jobs logs

  • Try the tests on different GeoServer releases

···

Regards,
Lorenzo Pini

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

Lorenzo Pini
Software Engineer

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

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

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

12

That is great, thank you for the update.

While the other teams have setup osgeo docker facilities, you are the first to try from GeoServer. I would like to ensure you have sufficient access (via a PSC member) to manage next week.

I am somewhat apprehensive, but looking forward to, seeing the initial testing results.

···

–
Jody Garnett

13

Some small feedback, as I went looking for test results.

I noticed the jobs uploading to:

[https://repo.osgeo.org/repository/geotools-releases/org/opengis/cite/ets-wcs11/1.13/ets-wcs11-1.13-ctl.zip](https://repo.osgeo.org/repository/geotools-releases/org/opengis/cite/ets-wcs11/1.13/ets-wcs11-1.13-ctl.zip)
···

Can you use the geoserver-releases repo for this work? I would also be happy to make an additional repo if it is appropriate.

Jody Garnett

14

Sure,
no problem.

I found existing artifacts there and just reused the same location.

···

Regards,
Lorenzo Pini

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

Lorenzo Pini
Software Engineer

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

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

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

15

Lorenzo:

Do you know when you will get back to this activity? I am planning out my A3 activities and would like to know if I can work towards passing cite tests.

···

–
Jody Garnett

16

Hi Jody,

Lorenzo is on leave this week. I know he submitted a PR for this work and he is addressing some points brought up by Andrea during
his review. Lorenzo will provide more information as he comes back next week.

Regards,
Alessandro

On Mon, Jul 20, 2020 at 3:51 AM Jody Garnett <jody.garnett@anonymised.com03…> wrote:

Lorenzo:

Do you know when you will get back to this activity? I am planning out my A3 activities and would like to know if I can work towards passing cite tests.

–
Jody Garnett

On Thu, 28 May 2020 at 08:18, Lorenzo Pini <lorenzo.pini@anonymised.com> wrote:

Sure,
no problem.

I found existing artifacts there and just reused the same location.

Regards,
Lorenzo Pini

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

Lorenzo Pini
Software Engineer

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

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

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

On Wed, May 27, 2020 at 8:20 PM Jody Garnett <jody.garnett@anonymised.com> wrote:

Some small feedback, as I went looking for test results.

I noticed the jobs uploading to:

[https://repo.osgeo.org/repository/geotools-releases/org/opengis/cite/ets-wcs11/1.13/ets-wcs11-1.13-ctl.zip](https://repo.osgeo.org/repository/geotools-releases/org/opengis/cite/ets-wcs11/1.13/ets-wcs11-1.13-ctl.zip)

Can you use the geoserver-releases repo for this work? I would also be happy to make an additional repo if it is appropriate.

Jody Garnett

On Fri, 22 May 2020 at 12:53, Jody Garnett <jody.garnett@anonymised.com> wrote:

That is great, thank you for the update.

While the other teams have setup osgeo docker facilities, you are the first to try from GeoServer. I would like to ensure you have sufficient access (via a PSC member) to manage next week.

I am somewhat apprehensive, but looking forward to, seeing the initial testing results.

–
Jody Garnett

On Fri, 22 May 2020 at 09:45, Lorenzo Pini <lorenzo.pini@anonymised.com> wrote:

Dear Jody,
I’m working on setting up the CITE tests automation.

Here is a brief update on the current status:

  • The required “ets-*” artifacts are being built on Jenkins. The deploy phase is currently missing, but it is not blocking as we only have a single server at the moment.

  • The teamengine-docker image is being built on Jenkins.

  • The cite-tests is now working on Jenkins and a first test shows that the cite tests are able to run against the latest GeoServer master.

  • I did a small improvement on the bash scripts to manage the exit code but I think a change in the teamengine-core java code will be needed to properly address this

I’ll continue next week with:

  • Completing the deploy of all the artifacts and docker images in maven repo and dockehub

  • Improve the readability of the jobs logs

  • Try the tests on different GeoServer releases

Regards,
Lorenzo Pini

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

Lorenzo Pini
Software Engineer

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

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

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

On Mon, Apr 6, 2020 at 8:53 PM Jody Garnett <jody.garnett@anonymised.com> wrote:

Alessandro:

We now have repo.osgeo.org operational, the builds should hopefully switch over in the next couple of days.

I have created https://repo.osgeo.org/repository/geoserver-docker/ for you to try out.

–
Jody Garnett

On Tue, 3 Mar 2020 at 09:48, Jody Garnett <jody.garnett@anonymised.com> wrote:

For repo, would having an osgeo nexus repo help as a place to store the docker images?

–
Jody Garnett

On Tue, 3 Mar 2020 at 01:41, Alessandro Parma <alessandro.parma@…1268…> wrote:

Thanks for your feedback

My answers inline below

I think managing the docker builds in the “build” directory is appropriate. Is it worth co-locating these with their cite data directory configuration (to make each folder more self contained)?

I agree. I would move the datadirs everything in the build/cite dir along with the docker related file, ok?

aside: In the past when faced with builds grabbing status codes we would grep through the output for failure, not sure how stable that is.

Ok, thank you. I’ll dig a little deeper into to try to avoid grepping the logs, if possible.

There is not an official repository on docker hub for this, we should set this up (I am not sure what is needed).

I think we should create an Organization and a team with members allowed to push the docker image to the hub.

On Fri, Feb 28, 2020 at 7:26 PM Jody Garnett <jody.garnett@anonymised.com> wrote:

Thank you for the update!

I think managing the docker builds in the “build” directory is appropriate. Is it worth co-locating these with their cite data directory configuration (to make each folder more self contained)?

aside: In the past when faced with builds grabbing status codes we would grep through the output for failure, not sure how stable that is.

There is not an official repository on docker hub for this, we should set this up (I am not sure what is needed).

–
Jody Garnett

On Fri, 28 Feb 2020 at 09:50, Alessandro Parma <alessandro.parma@anonymised.com> wrote:

HI Jody, All,

Status update with a couple of questions about the source code management and deployment of this work:

I added more builds for the ets suites, updated list:

  • wms11

  • wms13

  • wfs10

  • wfs11

  • wcs10

  • wcs11

  • wcs20

  • wfs20

Then created a build for the teamengine-docker fork to build the docker image for teamengine with the suites and tools that we need.
The docker image includes all of the sutes that we use and a single docker images can be used by all cite test runs (there is
nothing test-specific in it). This build is currently hosted on this build server because I had some issues with the build on geoserver
build server that I still need to address… The docker image is currently pushed here on the docker hub (more on this later)

I then created a parameterized build to run the tests. It is currently building from my GeoServer fork where I pushed the docker-compose files
and the other auxiliary files required to run the tests. My idea, and I’d like to have feedback from you as well as from the GeoServer
ML, is to add all the files required into the ‘build’ subdirectory of the repository. Would this be ok?
The file structure mimics that in our proposal where we have a global docker-compose.yml file with a ‘geoserver’ and '‘teamengine’ service
definition and subdirectory for every test suite with test specific files like “forms” for command line execution of a given test suite and a
docker-compose override file to spin up postgresql if required by the specific test. For data directories I’d use the ones that are
already available in the repository.

An example execution of this parametrized build is available here where I ran the WMS 1.1.1 suite against the latest geoserver master nightly.

The log files from the test run are stored as artifacts from the job run. There is still some work to do, notably, the job does not fail when a given
test fails (apparently due to the test.sh script in the teamengine suite swallowing the status of the tests. I still need to figure this out) and to add
more builds for the other suites. I’ll keep you informed on my progress on this.

Concerning the docker image(s) for teamengine-docker is there an official repository for GeoServer on the docker hub where I can push the image?

Thank you in advance for your feedback,
Alessandro

On Fri, Feb 21, 2020 at 6:00 PM Alessandro Parma <alessandro.parma@anonymised.com…> wrote:

Dear Jody, All

Just a quick update on this:
I set up a test build on the build server for one of the CITE tests to build and deploy the artifacts on the maven repository and
I am currently working on the the docker images and writing the docker-compose file to run the geoserver, postgres and teamengine
containers to execute the tests.
The build job is taking the Github branch and tags as parameters (with defaults) and is not tightly bound to the build environment so It
would be pretty straightforward to migrate it to another build server.
For the docker images and I don’t have something ready to show yet, I’ll let you know as soon as I do.

On Fri, Feb 14, 2020 at 6:42 PM Simone Giannecchini <simone.giannecchini@anonymised.com> wrote:

Hi Jody,
We are a little beyond schedule with this, the work has started but there is little to show.

We will send periodic updates to the psc and devel list starting next week.

Regards,
Simone Giannecchini

GeoServer Professional Services from the experts!
Visit http://bit.ly/gs-services for more information.

Ing. Simone Giannecchini
@simogeo
Founder/Director

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

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

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

On Thu, Feb 13, 2020 at 6:08 PM Jody Garnett <jody.garnett@anonymised.com> wrote:

Simone:

Next week’s Feb 18th meeting is our final meeting in February, is there any update from the Cite Automation work?

With the recent news from Planet Federal I am concerned about ability to deliver into build.geoserver.org environment.

–
Jody Garnett

–

Regards,
Simone Giannecchini.
GeoSolutions Director

  • sent from my mobile, apologies for brevity and typos-

–

Regards,

Alessandro Parma

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

Alessandro Parma
DevOps Engineer

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

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

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

–

Regards,

Alessandro Parma

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

Alessandro Parma
DevOps Engineer

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

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

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

–

Regards,

Alessandro Parma

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

Alessandro Parma
DevOps Engineer

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

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

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

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

–

Regards,

Alessandro Parma

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

Alessandro Parma
DevOps Engineer

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

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

Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.

17

Thanks, that is indeed an epic PR. I will have a look after this release.

···

–
Jody Garnett