[Geoserver-devel] Some troubles with the GeoServer release

GeoServer GeoServer Developer
1

Hi,
me and Martha have been going through the release process and reached the geoserver-release build.

It kept on failing, looking into it, I’ve found the disk was full. I’ve removed some very old builds and their workspaces, freeing some space, and started looking into cleaning up snapshots, as they are accumulating in the local maven repos of the builds (geoserver-main is 8GB…), as well as doing a pass of “clean” to remove the target folders, they are not needed after a build in any case.

Yet, even with space, the release job kept on failing… on this step:

image.png

echo “Allowing azure to write in the distribution folder”
chmod g+w distribution
chmod -R g+w /var/lib/jenkins/jobs/geoserver-release/builds/$BUILD_NUMBER/archive/distribution

This step does not make sense, because the archiving of the output is not yet done, it’s part of the “post-build” actions, which do happen later. And yet, post build actions do not allow to run a shell… so there is really no place to run it.

I’m removing it in order to get the release done, the above should work as a backup… that said, I’m not sure that can work, but maybe it can be moved in a downstream build (talks about azure, I guess it’s related to the windows installer build).

Cheers
Andrea

···

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

https://www.geosolutionsgroup.com/

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

2

Removing that step allowed the release job to succeed… and the windows build failed (again).
Seems due to permission issues, so those commands should probably be placed in the windows build?

Cheers
Andrea

(attachments)

image.png

···

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

https://www.geosolutionsgroup.com/

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

3

Andrea:

You are correct the permission changes allow the windows build to write the installer (when it is available) back to that location so it is available for the publish step to upload.

Juan may be able to troubleshot. For this release I should be able to login and get the windows installer from azure (not sure).

Not sure if it is in the release instructions yet but the Docker image instructions are here: https://github.com/geoserver/docker/blob/master/README.md

update the docker file version numbers

docker build -t geoserver-docker.osgeo.org/geoserver:2.22.0 .

docker login geoserver-docker.osgeo.org

docker push geoserver-docker.osgeo.org/geoserver:2.22.0

(attachments)

image.png

···

–
Jody Garnett

4

Andrea:

You are correct the permission changes allow the windows build to write the installer (when it is available) back to that location so it is available for the publish step to upload.

Yes, maybe we can move that step to the geoserver-windows-release job [1].

[1] https://build.geoserver.org/view/release/job/geoserver-windows-release/

Juan Luis Rodriguez Ponce

Mobile:

E-mail: juanluisrp@anonymised.com8…

https://www.geocat.net

Veenderweg 13

6721 WD Bennekom

The Netherlands

Tel: +31318416664

5

On Thu, Nov 17, 2022 at 8:16 PM Jody Garnett <jody.garnett@anonymised.com> wrote:

Andrea:

You are correct the permission changes allow the windows build to write the installer (when it is available) back to that location so it is available for the publish step to upload.

Yes… it was just executed at a time when the files it was meant to work on, did not exist yet. It could have never worked.

Not sure if it is in the release instructions yet but the Docker image instructions are here: https://github.com/geoserver/docker/blob/master/README.md

update the docker file version numbers

docker build -t geoserver-docker.osgeo.org/geoserver:2.22.0 .

docker login geoserver-docker.osgeo.org

docker push geoserver-docker.osgeo.org/geoserver:2.22.0

I see… verified I have working credentials.

I also see recent changes on the docker image script itself, but no releases… how is the project versioned, and how does it relate
to the GeoServer own versions?

Should be really included at the end of the release-publish script I guess, but I’d like to clarify versioning of the docker file before
moving in that direction.

Cheers
Andrea

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

https://www.geosolutionsgroup.com/

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

I’ve taken the liberty of adding that one chmod in the windows script and re-runit, and indeed the job is moving forward,
falling flat on its face due to credential issues later:

Access Denied: The Personal Access Token used has expired.

This message seems to be coming from Azure. I don’t know how to move forward from there.

Cheers
Andrea

···

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

https://www.geosolutionsgroup.com/

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

7

Andrea:

The installer has been generated and can be found here [1].

[1] https://build.geoserver.org/view/release/job/geoserver-release/92/artifact/distribution/2.22.0/

Juan Luis Rodriguez Ponce

E-mail: juanluisrp@anonymised.com

https://www.geocat.net

Veenderweg 13

6721 WD Bennekom

The Netherlands

Tel: +31318416664

---- On Fri, 18 Nov 2022 10:10:55 +0100 Andrea Aime andrea.aime@anonymised.com wrote —

I’ve taken the liberty of adding that one chmod in the windows script and re-runit, and indeed the job is moving forward,
falling flat on its face due to credential issues later:

Access Denied: The Personal Access Token used has expired.

This message seems to be coming from Azure. I don’t know how to move forward from there.

Cheers

Andrea

On Fri, Nov 18, 2022 at 9:02 AM Juan Luis Rodriguez Ponce <juanluisrp@anonymised.com> wrote:

–

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

https://www.geosolutionsgroup.com/

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

Andrea:

You are correct the permission changes allow the windows build to write the installer (when it is available) back to that location so it is available for the publish step to upload.

Yes, maybe we can move that step to the geoserver-windows-release job [1].

[1] https://build.geoserver.org/view/release/job/geoserver-windows-release/

Juan Luis Rodriguez Ponce

Mobile:

E-mail: juanluisrp@anonymised.com2488…

https://www.geocat.net

Veenderweg 13

6721 WD Bennekom

The Netherlands

Tel: +31318416664
8

Hi Juan,
thanks for doing that!

Looks like the release job was not used, it’s still red, so I assume you run the creation on your own.
What needs to be done, in order to get that job fixed and running automatically when we need to?

Cheers
Andrea

···

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 339 8844549

https://www.geosolutionsgroup.com/

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

---- On Fri, 18 Nov 2022 12:47:06 +0100 Andrea Aime <andrea.aime@anonymised.com> wrote —

Hi Juan,
thanks for doing that!

Looks like the release job was not used, it’s still red, so I assume you run the creation on your own.

What needs to be done, in order to get that job fixed and running automatically when we need to?

I guess I or Jody need to generate a Personal Access Token in Azure Dev, update the current secret (AZURE_WINDOWS_CREDENTIALS) used by the job in Jenkins. The project changed to a new organization and the old PAT stopped working. Probably Jody has enough permissions to update the secret.

Best regards,
Juan Luis.

10

Updated the Personal Access Token,

I note the chmod is failing as Jenkins does not have permission to modify exe uploaded by prior run. Deleting the file allowed to verify that the access token works (and installer was uploaded).

Trying to change the file group to jenkins so this should not happen in the future:

-rw-rw-r-- 1 azurebuild jenkins 110M Nov 18 16:19 GeoServer-2.22.0-winsetup.exe

But this did not resolve the issue; and chmod failed on the next attempt.

chmod: changing permissions of ‘/var/lib/jenkins/jobs/geoserver-release/builds/92/archive/distribution/2.22.0/GeoServer-2.22.0-winsetup.exe’: Operation not permitted

I expect that as a normal user jenkins cannot change ownership of a file (w access for the group is not sufficient for chown?)

···

–
Jody Garnett

11

I expect that as a normal user jenkins cannot change ownership of a file (w access for the group is not sufficient for chown?)

In Linux, only root can change ownership. Maybe you could sudo?

Carsten

···

Am 18.11.2022 um 17:32 schrieb Jody Garnett:

Updated the Personal Access Token,

I note the chmod is failing as Jenkins does not have permission to modify exe uploaded by prior run. Deleting the file allowed to verify that the access token works (and installer was uploaded).

Trying to change the file group to jenkins so this should not happen in the future:

-rw-rw-r-- 1 azurebuild jenkins 110M Nov 18 16:19 GeoServer-2.22.0-winsetup.exe

But this did not resolve the issue; and chmod failed on the next attempt.

chmod: changing permissions of ‘/var/lib/jenkins/jobs/geoserver-release/builds/92/archive/distribution/2.22.0/GeoServer-2.22.0-winsetup.exe’: Operation not permitted

I expect that as a normal user jenkins cannot change ownership of a file (w access for the group is not sufficient for chown?)

–
Jody Garnett

On Nov 18, 2022 at 4:39:37 AM, Juan Luis Rodriguez Ponce <juanluisrp@anonymised.com> wrote:

---- On Fri, 18 Nov 2022 12:47:06 +0100 Andrea Aime <andrea.aime@anonymised.com> wrote —

Hi Juan,
thanks for doing that!

Looks like the release job was not used, it’s still red, so I assume you run the creation on your own.

What needs to be done, in order to get that job fixed and running automatically when we need to?

I guess I or Jody need to generate a Personal Access Token in Azure Dev, update the current secret (AZURE_WINDOWS_CREDENTIALS) used by the job in Jenkins. The project changed to a new organization and the old PAT stopped working. Probably Jody has enough permissions to update the secret.

Best regards,
Juan Luis.

_______________________________________________
Geoserver-devel mailing list
[Geoserver-devel@lists.sourceforge.net](mailto:Geoserver-devel@lists.sourceforge.net)
[https://lists.sourceforge.net/lists/listinfo/geoserver-devel](https://lists.sourceforge.net/lists/listinfo/geoserver-devel)
12

You are correct; I think it is working now (used find to remove the file if it exists before changing ownership).

···

–
Jody Garnett

–
Jody Garnett