fix(ci): skip build when image tag already exists (DASOPS-2157) - #1700
Merged
andersondario-er merged 1 commit intoAug 14, 2026
Merged
Conversation
Artifact Registry has tag immutability enabled, so re-running develop.yml
or release.yml for an already-built commit fails when pushing the same
{branch}-{sha} tag. Add a check-if-image-exists guard (already used by
pr-envs.yml) and gate the build/push step on it; downstream deploy jobs
reuse the existing image.
andersondario-er
deleted the
fix-DASOPS-2157-image-tag-immutability-skip
branch
August 14, 2026 10:39
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
1 participant
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.
Summary
Builds re-run for an already-built commit fail when pushing the immutable
{branch}-{sha}image tag (cannot update tag ... The repository has enabled tag immutability). This adds a guard so an existing image is detected and the build/push is skipped, letting the deploy jobs reuse it.Changes
Fixed
develop.ymlandrelease.ymlnow check whether the target image tag already exists before building, and skipBuild and pushwhen it does. This mirrors the guardpr-envs.ymlalready uses, so all three workflows behave consistently on re-runs.Technical Details
Check if image already existsstep runsgcloud artifacts docker images describeand sets anexistsoutput;Build and pushgainsif: steps.image-check.outputs.exists != 'true'.--immutable), so an existing image is the same source — a skip is safe. The only residual edge is base-image drift over time, the same tradeoff already accepted for PR envs.Files Changed
2 files changed, 32 insertions(+)
.github/workflows/develop.yml.github/workflows/release.ymlJira: https://allenai.atlassian.net/browse/DASOPS-2157