- Mar 15, 2025
-
-
Georges Racinet authored
-
- Feb 13, 2025
-
-
Georges Racinet authored
Now obviously, it needs two keys, which are `final` and `intermediate`
-
- Jan 23, 2025
-
-
Georges Racinet authored
-
Georges Racinet authored
The messages were misleading, we no longer push to docker.io
-
- Jan 09, 2025
-
-
Georges Racinet authored
-
Georges Racinet authored
In case the release process has to be resumed, it is useful to start from the image in orus (the one in registry.h.n has potentially already moved on).
-
Georges Racinet authored
No mention of Docker Hub anymore, and making explicit that this is about the testing images.
-
Georges Racinet authored
We do not want to push all testing intermediate images to Docker Hub. Pushing to registry.orus.io warms before the final version tagging and the resulting tag is useful if for some reason the release process is interrupted and has to be finished later on.
-
Georges Racinet authored
-
Georges Racinet authored
The dispatching will now be done based on the version status (rc or final). Perhaps later we will need to reintroduce extra repositories (for customers), but it will have to depend on the status.
-
Georges Racinet authored
It will be necessary for dispatching between orus.io, foss.h.n and docker.io
-
Georges Racinet authored
-
- Dec 12, 2024
-
-
Georges Racinet authored
and parsing it from the job log full line while we're at it.
-
- Dec 11, 2024
-
-
Georges Racinet authored
-
- Oct 24, 2024
-
-
Georges Racinet authored
The immediate motivation was to have the social media content without submitting image id (useful after push retries).
-
Georges Racinet authored
We were originally conservative, avoiding growth in registry.h.n and relying on garbage collection to do that. But now we have S3 backend and Docker Hub is not the infinite space it used to be.
-
- Sep 19, 2024
-
-
Georges Racinet authored
It is in particular useful because the registries I am pushing to depends on the tagged versions.
-
Georges Racinet authored
flake8 errors and one additional line feed in order not to miss the prepared message after the long operation log
-
Georges Racinet authored
This avoids perhaps some tag ambiguities when using podman.
-
- Sep 26, 2024
-
-
Georges Racinet authored
-
- Sep 15, 2024
-
-
Georges Racinet authored
It is of course much heavier than using the `crane:debug` image, yet much saner for scripting than Busybox sh.
-
- Sep 13, 2024
-
-
Georges Racinet authored
-
Georges Racinet authored
It's become very boring to build manually the likes of ``` ./registry-pull-heptapod-push-docker \ --push \ --podman \ --tag 0-32-testing \ --verify-hg-tag heptapod-0.32.1-1 \ --expected-image-id 0e976fdfa6733d4298025cd0b98ae36384863c8dd8d60ac7f9f979bb5d05b259 ``` Next step should be to parse the SHA256 directly from the CI job.
-
- Aug 22, 2024
-
-
Georges Racinet authored
-
Georges Racinet authored
It was way too magical to be used with confidence
-
- Aug 12, 2024
-
-
Georges Racinet authored
-
- Jun 27, 2024
-
-
Georges Racinet authored
Triggered by the new minimal Python version, was a bit overdue
-
Georges Racinet authored
This allows to accomodate typically private registries (e.g., support customers)
-
Georges Racinet authored
This makes the minimum Python version to be 3.11 Usage of `docker` or `podman` executables tends to depend on the host only, hence it is a relevant use case (more to come later).
-
- Feb 07, 2024
-
-
Georges Racinet authored
Since the introduction of the random initial password, each time I forgot to use `--root-password`, I had to start over again or go through the lengthy and manual password change procedure, and chose of course the GDK/HDK default password. This change would be obviously a security problem if someone had the weird idea to use this development helper to launch an internet facing instance, whence the terse messages not to do that.
-
Georges Racinet authored
Still kept a switch to avoid it.
-
- Mar 21, 2024
-
-
Georges Racinet authored
At this point the testing image will be pushed to `heptapod/heptapod` only, but we still push the other tags, e.g., `1.3.0`, `1-3-latest` to the previously used `octobus/heptapod`
-
Georges Racinet authored
-
- Oct 16, 2023
-
-
Georges Racinet authored
Docker qualifies it with the hashing algorithm, as in `sha256:XXX` whereas Podman does not. We found it hard to remember.
-
- May 31, 2023
-
-
Georges Racinet authored
This is more convenient than picking the temporary password from `/etc/gitlab`, and can help reproducing CI failures, since the environment variable is used in `heptapod-tests` CI.
-
- May 15, 2023
-
-
Georges Racinet authored
-
Georges Racinet authored
In Docker official terminology, the tag is the whole, e.g., `heptapod/octobus:testing`. In practice, that is a pain.
-
Georges Racinet authored
This is something Docker would do.
-
- Dec 16, 2022
-
-
Georges Racinet authored
-
Georges Racinet authored
-