Hi,
First version of the script can be found here:
https://github.com/geoserver/docker/pull/18
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 r
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
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
(buil
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
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
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):
ht
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
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 Jak
Hi,
I will be looking into automating this shortly.
Greetings,
Johannes
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 wrote:
Hi everybo
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 wrote:
> Hi everybody,
>
> in the repo for the GeoServer Docker image the version is already set to
> '2.22.0' (https://github.com/geoserver/doc
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 t
11 matches
Mail list logo
