We are in the middle of a long drawn out release process, please do not merge any PRs until you here back on this email thread.
Presently:
GeoTools main is 33-SNAPSHOT and job is enabled,
32.x branch is created with a job enabled
GeoWebCache main is 1.27-SNAPSHOT,
but we have not set up 1.26.x jobs yet
GeoServer mains is not yet updated, so I have disabled the build job to prevent confusion
I am downing tools for the day and will resume tomorrow.
Jody Garnett
Hi Jody,
we haven’t had a freeze in years, normally the new stable branch is created and we move on
without any blockage.
What’s different this time that requires a freeze, and how long will it take?
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
Jody Garnett
New stable 2.26.x branch is created.
Please double check if you merged any PR to main branch during the freeze.
Jobs are running now and I will check in the morning if they succeeded
Jody Garnett
Jody Garnett
New stable 2.26.x branch is created.
Excellent
- Please double check if you merged any PR to main branch during the freeze.
Can you clarify what are the supposed consequences of having merged during “freeze” and what you expect to be done?
- Jobs are running now and I will check in the morning if they succeeded
All seems green
Cheers
Andrea
On Fri, Sep 20, 2024 at 9:55 AM Jody Garnett <jody.garnett@anonymised.com> wrote:
Check the 2.26.x branch to double check your commits are present. I think I got everything but …
I also have been doing the usual fun checking for issues that need to be closed as their PR has been merged.
Check the 2.26.x branch to double check your commits are present. I think I got everything but …
Agreed, it seems you got everything.
I also have been doing the usual fun checking for issues that need to be closed as their PR has been merged.
Yes, that always happens. We need to migrate issues to Github, then we can have them close on PR merge
(but can we associate them to release milestone as well, on backport? who knows)
Cheers
Andrea
On Fri, Sep 20, 2024 at 6:56 PM Jody Garnett <jody.garnett@anonymised.com> wrote:
Downloads available for preflight testing: https://build.geoserver.org/view/release/job/geoserver-release/151/artifact/distribution/2.26.0/
Jody Garnett
Jody Garnett
Something is wrong with the docker build: https://build.geoserver.org/view/geoserver/job/geoserver-release-docker/
Not sure what parent snapshot is?
Jody Garnett
Jody Garnett
Jody Garnett
Hi Niels,
I am troubleshooting the 2.26.0 release and notice some of the dependency updates you have merged recently have broken the docker build.
Is there any way to set up a workflow to verify changes function; so they can be tested prior to merging?
The specific PR seems to be this one: https://github.com/geoserver/docker/pull/90
I am going to try building locally, and revert this commit if I must.
Jody Garnett
Not sure what parent snapshot is?
Jody Garnett
Jody Garnett
Jody Garnett
I was able to follow the manual release process: https://github.com/geoserver/docker/blob/master/RELEASE.md
Looking online I found the following: https://github.com/moby/buildkit/issues/4024 with the indication that:
The problem will persist until we take the buildkit node offline, so it never seems to recover.
For now the release is unblocked; but some kind of care is needed on the Jenkins builder server.
Jody Garnett
Jody Garnett
Not sure what parent snapshot is?
Jody Garnett
Jody Garnett
Jody Garnett
The windows build did not show up for the party; some credentials need to be updated. I trust it will be addressed tomorrow.
Jody Garnett
Jody Garnett
Jody Garnett
Windows build is now available (credentials had expired).
Jody Garnett
Jody Garnett
Jody Garnett
Jody Garnett
Hi,
Your manual build of the Geoserver container seems to have gone wrong. The Geoserver version is 2.25.2 and the architecture is arm64.
docker run docker.osgeo.org/geoserver:2.26.0
Unable to find image ‘docker.osgeo.org/geoserver:2.26.0’ locally
2.26.0: Pulling from geoserver
Digest: sha256:f47225a2650ee231a2ef1a20b81f18ece06081028e5e8f5dd4d162ba90ca1fe7
Status: Downloaded newer image for docker.osgeo.org/geoserver:2.26.0
WARNING: The requested image’s platform (linux/arm64) does not match the detected host platform (linux/amd64/v2) and no specific platform was requested
Welcome to GeoServer 2.25.2
Regards
Roar Brænden
Jody Garnett
Jody Garnett
Not sure what parent snapshot is?
Jody Garnett
Jody Garnett
Jody Garnett