Hi again,
I intend to setup an github action, which periodically checks for new geoserver releases.
If a new one is available, the action should build, test and finally push the image to the osgeo repo.
Therefore i need to configure my credentials in the settings of the github repo, but i am missing permissions for that.
Why not have it as part of the release scripts instead… a periodic check could have the docker
be available either before announcement (sometimes we have a few days in between artifacts and announcement)
or after the release is available to the general public.
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
Personally i dont really care if a github action or a shell script is used to get the image build and published.
But i like the idea to have the docker things all in one place / repo instead of spreading it over several repos.
One could also use a trigger / notify in the mentioned scripts to start the build in github actions so that the timing should be no issue then.
Are there other opinions ?
Greetings,
Johannes
···
Am 26.01.23 um 14:12 schrieb Andrea Aime:
Why not have it as part of the release scripts instead… a periodic check could have the docker
be available either before announcement (sometimes we have a few days in between artifacts and announcement)
or after the release is available to the general public.
Hi again,
I intend to setup an github action, which periodically checks for new geoserver releases.
If a new one is available, the action should build, test and finally push the image to the osgeo repo.
Therefore i need to configure my credentials in the settings of the github repo, but i am missing permissions for that.
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
--
Dipl.-Geogr. Johannes Weskamm
— Anwendungsentwickler —
terrestris GmbH & Co. KG
Kölnstraße 99
53111 Bonn
Tel: +49 (0)228 / 96 28 99 -51
Fax: +49 (0)228 / 96 28 99 -57
Email: [weskamm@anonymised.com](mailto:weskamm@anonymised.com08...)
Web: [https://www.terrestris.de](https://www.terrestris.de)
Amtsgericht Bonn, HRA 6835
Komplementärin: terrestris Verwaltungsgesellschaft mbH
vertreten durch: Torsten Brassat, Marc Jansen
Informationen über Ihre gespeicherten Daten finden Sie auf
unserer Homepage unter folgendem Link:
[https://www.terrestris.de/datenschutzerklaerung/](https://www.terrestris.de/datenschutzerklaerung/)
Personally i dont really care if a github action or a shell script is used to get the image build and published.
But i like the idea to have the docker things all in one place / repo instead of spreading it over several repos.
One could also use a trigger / notify in the mentioned scripts to start the build in github actions so that the timing should be no issue then.
Are there other opinions ?
Greetings,
Johannes
Am 26.01.23 um 14:12 schrieb Andrea Aime:
Why not have it as part of the release scripts instead… a periodic check could have the docker
be available either before announcement (sometimes we have a few days in between artifacts and announcement)
or after the release is available to the general public.
Hi again,
I intend to setup an github action, which periodically checks for new geoserver releases.
If a new one is available, the action should build, test and finally push the image to the osgeo repo.
Therefore i need to configure my credentials in the settings of the github repo, but i am missing permissions for that.
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
I think the shell script could be in the https://github.com/geoserver/docker repository. perhaps build/release.sh if we wish to be consistent.
Then I would configure build.geoserver.org to checkout the docker file and run the script with the version being published (example 2.22.1). I could set up the job but would like to make sure you have permissions to run it for troubleshooting.
I guess we can move the discussion now to that PR.
Greetings,
Johannes
···
Am 31.01.23 um 17:14 schrieb Jody Garnett:
I think the shell script could be in the https://github.com/geoserver/docker repository. perhaps build/release.sh if we wish to be consistent.
Then I would configure build.geoserver.org to checkout the docker file and run the script with the version being published (example 2.22.1). I could set up the job but would like to make sure you have permissions to run it for troubleshooting.
Personally i dont really care if a github action or a shell script is used to get the image build and published.
But i like the idea to have the docker things all in one place / repo instead of spreading it over several repos.
One could also use a trigger / notify in the mentioned scripts to start the build in github actions so that the timing should be no issue then.
Are there other opinions ?
Greetings,
Johannes
Am 26.01.23 um 14:12 schrieb Andrea Aime:
Why not have it as part of the release scripts instead… a periodic check could have the docker
be available either before announcement (sometimes we have a few days in between artifacts and announcement)
or after the release is available to the general public.
Hi again,
I intend to setup an github action, which periodically checks for new geoserver releases.
If a new one is available, the action should build, test and finally push the image to the osgeo repo.
Therefore i need to configure my credentials in the settings of the github repo, but i am missing permissions for that.
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
--
Dipl.-Geogr. Johannes Weskamm
— Anwendungsentwickler —
terrestris GmbH & Co. KG
Kölnstraße 99
53111 Bonn
Tel: +49 (0)228 / 96 28 99 -51
Fax: +49 (0)228 / 96 28 99 -57
Email: [weskamm@anonymised.com](mailto:weskamm@anonymised.com08...)
Web: [https://www.terrestris.de](https://www.terrestris.de)
Amtsgericht Bonn, HRA 6835
Komplementärin: terrestris Verwaltungsgesellschaft mbH
vertreten durch: Torsten Brassat, Marc Jansen
Informationen über Ihre gespeicherten Daten finden Sie auf
unserer Homepage unter folgendem Link:
[https://www.terrestris.de/datenschutzerklaerung/](https://www.terrestris.de/datenschutzerklaerung/)