ci: publish versioned Docker Hub tags on release tags - #661
Merged
Conversation
Pushing a git tag like esplora_v2.10 now builds and publishes blockstream/esplora:v2.10 (plus per-arch v2.10-amd64/v2.10-arm64 tags and a multi-arch manifest) to Docker Hub, alongside the existing :latest tags that track master. This gives users immutable, pinnable image tags for reproducible deployments and rollbacks, using the existing GitLab CI pipeline and credentials; no new registry or secrets involved.
Randy808
approved these changes
Aug 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Versioned Docker images via the existing pipeline
Today the GitLab CI pipeline only ever pushes
blockstream/esplora:latest, so there is no way to pull "the image for release X" so pinning and rollbacks require digests.This PR adds tag-triggered release jobs to the existing pipeline: pushing a git tag like
esplora_v2.10builds the image from that tagged commit and publishes:blockstream/esplora:v2.10— multi-arch manifest (amd64 + arm64)blockstream/esplora:v2.10-amd64,blockstream/esplora:v2.10-arm64latestcontinues to trackmasterexactly as before.Design notes
.build_esplora_latestjobs (same base-image pin viaBASE_TAG, sameFOOT_HTMLcommit stamp, same buildx/cache setup), so a release build is identical to a master build of the same commit, just with a version tag.$CI_COMMIT_TAG =~ /^esplora_v/); branch, MR, and trigger pipelines are unaffected.This is the alternative to #629: it delivers the versioned/pinnable images that PR is after, but through the pipeline that already builds and tests our published images, and matching our actual
esplora_vX.YYtag format.Validation
gitlab/build.ymlparses as valid YAML; the folded multi-line commands were verified to collapse to the intended shell commands.$CI_COMMIT_BRANCH, latest/test jobs useonly: branches/master, the GitHub status jobs require trigger pipelines).esplora_v*tag push on the repo that runs CI.