migrate cri-o CI to gcp#30733
Conversation
|
/retest |
1 similar comment
|
/retest |
|
/retest |
1 similar comment
|
/retest |
|
/pj-rehearse |
|
/test pj-rehearse |
11 similar comments
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/retest |
|
/test pj-rehearse |
3 similar comments
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/test pj-rehearse |
|
/retest |
3 similar comments
|
/retest |
|
/retest |
|
/retest |
There was a problem hiding this comment.
I think once you are the OWNER of bastionhost, no need to change this file.
There was a problem hiding this comment.
I guess you can drop the gpei, jianlinliu and jianli-wei from the OWNER list for the buildhost ref.
|
btw, do you mind squashing multiple commit into one after fixed all the comments. |
|
/retest |
|
There are two comments are not resolved yet: |
1747ed4 to
73992a1
Compare
There was a problem hiding this comment.
I meant you can create a plain OWNER file under gcp/{provision,deprovision}/buildhost/, then place your team member as owners for the newly created steps, but not touch with parent folder's OWNER list.
|
/retest |
|
@jianlinliu if there are remaining issues in your work day, would you mind if we handled them as a follow up? our CI has been broken for a week and a half in anticipation of this, so we're eager to merge this to have some working CI in the interim |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, jianlinliu, rphillips, wgahnagl 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 |
I will submit a followup PR to fix the remaining issues to save time. |
|
@wgahnagl: The following tests 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/test-infra repository. I understand the commands that are listed here. |
|
@wgahnagl: Updated the following 2 configmaps:
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 kubernetes/test-infra repository. |
moves the cri-o CI away from equinix to GCP