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. Jody -- Jody Garnett On Tue, Jan 31, 2023 at 10:11 AM Johannes Weskamm <wesk...@terrestris.de> wrote: > Ok, then i need hints what to do. Do you need a shell script which sets up > the image? Anything else? > > PR against https://github.com/geoserver/geoserver/tree/main/build ? > > > Greetings, > > Johannes > > > Am 28.01.23 um 08:46 schrieb Jody Garnett: > > I would prefer to manage the secrets in one location (build.geoserver.org) > rather than spread across services. > > In the last year I had to check our history as travis had been compromised > (which we had not used for a long time, and never for deploy). > -- > Jody Garnett > > > On Fri, Jan 27, 2023 at 1:28 PM Johannes Weskamm <wesk...@terrestris.de> > wrote: > >> 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. >> >> Scripts are here (*_release.sh): >> https://github.com/geoserver/geoserver/tree/main/build >> >> Cheers >> Andrea >> >> On Thu, Jan 26, 2023 at 10:24 AM Johannes Weskamm <wesk...@terrestris.de> >> wrote: >> >>> 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. >>> >>> Not sure if Jody can help here? >>> >>> This is what has to be done: >>> >>> >>> https://docs.github.com/en/actions/security-guides/encrypted-secrets#creating-encrypted-secrets-for-a-repository >>> >>> >>> Greetings, >>> >>> Johannes >>> >>> >>> Am 26.01.23 um 09:59 schrieb Jakob Miksch: >>> >>> Alright, thanks for the quick response. An automatic publication of the >>> images would indeed be very useful. >>> >>> Am 26.01.23 um 09:53 schrieb Jody Garnett: >>> >>> Indeed we need a volunteer to do the publish; or indeed to add a job to >>> our build server. >>> -- >>> Jody Garnett >>> >>> >>> On Thu, Jan 26, 2023 at 9:33 AM Jakob Miksch <ja...@meggsimum.de> wrote: >>> >>>> Hi everybody, >>>> >>>> in the repo for the GeoServer Docker image the version is already set >>>> to >>>> '2.22.0' (https://github.com/geoserver/docker), but the image is not >>>> published to the registry yet >>>> ( >>>> https://docker.osgeo.org/#browse/browse:geoserver-docker:v2%2Fgeoserver%2Ftags >>>> ). >>>> >>>> Who is typically doing the publishing? >>>> >>>> Best regards, >>>> Jakob >>> >>> >>> _______________________________________________ >>> Geoserver-devel mailing list >>> Geoserver-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel >>> >> >> >> -- >> >> 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 >> >> >
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
