Auto-trigger test image build on release branch push - #559
Open
niyomukiza-mechack wants to merge 1 commit into
Open
Auto-trigger test image build on release branch push#559niyomukiza-mechack wants to merge 1 commit into
niyomukiza-mechack wants to merge 1 commit into
Conversation
niyomukiza-mechack
requested review from
a team,
eniko-dif and
jlegrone
as code owners
August 31, 2026 02:04
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 was changed
I spent some time reading through the release doc to understand the process and pain points. Release automation is a new area for me. This felt like a good starting point: Step 4 ("Publish release branch image for testing") already works, it just requires someone to manually trigger it from the Actions UI after pushing a release branch.
I added
release/**to thepush.branchestrigger inpublish-image.yml. This makes the test image build kick off automatically whenever someone pushes a release branch so no need for manually going to the Actions tab to run the workflow.Why?
Previously, Step 4 of the release process(Link -> https://docs.google.com/document/d/1Ck_k_6xAjdVv-d7xjQfdI1ZXWu9L0xzBvuqs5NS4q24/edit?tab=t.0) required someone to manually run the publish image workflow from the GitHub Actions UI after pushing a release branch. This change auto-triggers it on
push to
release/**branches.Checklist
Closes
How was this tested:
Tested pre-merge by pushing a
release/test-491branch with this change. The workflow triggered automatically and completed successfully and pushed to docker.FYI: Seems like I can't delete them, @jaypipes if you have access can you delete the
release/test-491tags please? :)3. Any docs updates needed?