METAL-1726: Add yet another stage for ironic-image#8913
METAL-1726: Add yet another stage for ironic-image#8913locriandev merged 1 commit intoopenshift-eng:openshift-4.22from
Conversation
|
@elfosardo: This pull request references METAL-1726 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
without this I think openshift/ironic-image#786 will break the internal builds |
|
cc @joepvd @locriandev |
locriandev
left a comment
There was a problem hiding this comment.
/hold
This change can only happen once ironic's Dockerfile grows an extra build layer, otherwise we'd have rebase failures and stop building it.
Apart from this, the correct syntax would be:
from:
builder:
- member: openshift-enterprise-base-rhel9-minimal
- member: openshift-enterprise-base-rhel9-minimal
member: openshift-enterprise-base-rhel9-minimal
|
@elfosardo the chicken'n'egg problem can be solved by merging this PR right after the ironic one :) Next build would find consistent config with upstream. Worst case scenario, we might miss some cycles. |
|
@locriandev ok so the "builder" entry it does not depend on the name of the stage, it's just a list? |
|
@elfosardo that's right, |
e0fe39e to
8ad18bc
Compare
8ad18bc to
d5b13b3
Compare
d5b13b3 to
e14ff15
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: locriandev The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
@elfosardo: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
dc36eb1
into
openshift-eng:openshift-4.22
No description provided.