-
Notifications
You must be signed in to change notification settings - Fork 256
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.
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
🌱 Move container build to gh runner #1861
🌱 Move container build to gh runner #1861
Conversation
029ab25
to
f7c48a2
Compare
ab36e91
to
32e3a26
Compare
/cc @kashifest |
034b980
to
086b4ad
Compare
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kashifest The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/unhold We have the secrets and project-infra PR inplace |
/unhold |
@tuminoid Could you please re-lgtm? I accidentally force pushed this PR when I tested it upstream. |
086b4ad
to
deecc18
Compare
Signed-off-by: Huy Mai <[email protected]>
deecc18
to
553e907
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/cherry-pick release-0.5 release-0.6 |
/cherry-pick release-0.5 release-0.6 |
@mquhuy: new pull request created: #1909 In 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 kubernetes-sigs/prow repository. |
@mquhuy: new pull request could not be created: failed to create pull request against metal3-io/baremetal-operator#release-0.5 from head metal3-io-bot:cherry-pick-1861-to-release-0.5: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for metal3-io-bot:cherry-pick-1861-to-release-0.5."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request","status":"422"} In 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 kubernetes-sigs/prow repository. |
/cherry-pick release-0.6 |
@mquhuy: new pull request created: #1910 In 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 kubernetes-sigs/prow repository. |
This assumes metal3-io/project-infra#833 was merged, and that
QUAY_IO_USERNAME
andQUAY_IO_TOKEN
secrets exist, for pushing the image toquay.io
.An example of complete workflow (except for the push part):
https://github.com/metal3-io/baremetal-operator/actions/runs/10280659565/job/28448467379?pr=1861
/hold to wait for the secrets.