Skip to content

Release: when a minor release branch is created, the initial image for tag :release-x is not triggered #2449

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
tuminoid opened this issue May 8, 2025 · 2 comments
Open

Release: when a minor release branch is created, the initial image for tag :release-x is not triggered #2449

tuminoid opened this issue May 8, 2025 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@tuminoid
Copy link
Member

tuminoid commented May 8, 2025 •
edited
Loading

What steps did you take and what happened:

Make a minor or RC release by creating appropriate release note PR, which leads to release branch creation upon merging.

What did you expect to happen:

A container image is built for the tag v1.10.0 but also release-1.10 which is used in testing.

Anything else you would like to add:

Note that container image build job and release image job do same thing, but only the latter matters in case of release cutting/branch creation due "workflow cannot implicitly initiate another workflow" rule.

/kind bug
@metal3-io-bot metal3-io-bot added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels May 8, 2025
@tuminoid tuminoid mentioned this issue May 8, 2025
Open
@tuminoid
Copy link
Member Author

tuminoid commented May 8, 2025

This is happening in CAPM3, IPAM and BMO.

@tuminoid tuminoid mentioned this issue May 8, 2025
Open
@tuminoid
Copy link
Member Author

/triage accepted

@metal3-io-bot metal3-io-bot added triage/accepted Indicates an issue is ready to be actively worked on. and removed needs-triage Indicates an issue lacks a `triage/foo` label and requires one. labels May 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tuminoid @metal3-io-bot