ci: build each release image once and unblock the independent release jobs - #486
Open
boddumanohar wants to merge 5 commits into
Open
boddumanohar wants to merge 5 commits into
boddumanohar wants to merge 5 commits into
Conversation
Repo: Release used to be one long conga line that built the operator and rebalancer images twice. Now each image is built once, pushed straight to Quay from the build (no second buildx round-trip just to reach it), and everything that doesn't touch an image runs alongside the builds instead of behind them. The OLM bundle and the operator chart both wait on the operator images (nothing else) and race each other; only the final FTPS publish waits on everything. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
boddumanohar
force-pushed
the
ci/parallelize-release-pipeline
branch
from
September 8, 2026 08:58
750371a to
fa312f0
Compare
noctarius
force-pushed
the
main
branch
2 times, most recently
from
September 9, 2026 10:21
60dceb7 to
fbaabe4
Compare
Quay is where the OLM bundle resolves image digests from, so it only needs a tag when the operator build runs as part of an actual release (this job invoked via workflow_call from repo_release.yaml's v* tag trigger). Gate the Quay login and the Quay tag out of DockerHub/ECR pushes made on ordinary branch pushes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…mage operator_build.yaml goes back to DockerHub + ECR only, dropping the conditional Quay push added in the previous commit. Quay only matters for a release (make bundle resolves image digests straight from its registry API), so keep it entirely out of the build workflow, which also runs on every plain branch push. operator_release.yaml now retags the already-built DockerHub manifest to Quay with `docker buildx imagetools create` before generating the bundle. This copies the multi-arch manifest across registries without rebuilding, so the image is still built exactly once; Quay is written to only during a release-operator run. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
release-operator populates Quay itself now, by retagging build-operator's DockerHub images, rather than build-operator pushing there directly. Update the comment above release-operator to describe that instead of the old (now incorrect) claim that build-operator writes to Quay. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The comments across operator_build.yaml, operator_release.yaml, and repo_release.yaml restated structure the code already makes clear. Cut them down to the one non-obvious reason each job or step needs, dropping the rest. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.
What
Turns
Repo: Releasefrom one long serial chain into a dependency graph, and builds each operator image once instead of twice.Key changes
operator_build.yamlbuilds the operator and rebalancer images once, to DockerHub + ECR.operator_release.yamlretags that same multi-arch manifest to Quay (docker buildx imagetools create, no rebuild) before generating the OLM bundle — Quay is only ever written to during a release, never on a plain branch push.build-csiandbuild-operatorno longer serialize;release-operatorandpackage-operator-chartboth hang offbuild-operatorinstead of queuing behind each other.versionlabel now tracks the real release tag instead of a hardcoded0.1.0, and the rebalancer image gets it too.Testing
needs:graph matches the diagram above..claude/skills/house-style/scripts/quality-gate.sh --changed— all 9 gates pass.v*tag. Worth a throwaway tag before trusting it for a real release.🤖 Generated with Claude Code