-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Add changes for OCP Sustaining 4.12, 4.13, 4.14 autorelease jobs #64641
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
Add changes for OCP Sustaining 4.12, 4.13, 4.14 autorelease jobs #64641
Conversation
a17fab4
to
04baf94
Compare
/pj-rehearse list |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse max |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.12-automated-release-gcp-ipi-sdn-f999 |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
04baf94
to
50abd39
Compare
[REHEARSALNOTIFIER]
A total of 28 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
/pj-rehearse max |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/retest |
/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.13-automated-release-azure-ipi-fips-f999 |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.12-automated-release-gcp-ipi-sdn-f999 |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.13-automated-release-stable-4.13-upgrade-from-stable-4.12-azure-ipi-fips-f999 |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.14-automated-release-stable-4.14-upgrade-from-stable-4.14-azure-upi-f999 |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.14-automated-release-stable-4.14-upgrade-from-stable-4.14-aws-ipi-f999 |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.14-automated-release-azure-ipi-fips-f999 |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.14-automated-release-azure-ipi-fips-f999 |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.14-automated-release-stable-4.14-upgrade-from-stable-4.13-azure-ipi-fips-f999 |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
/lgtm |
/assign @liangxia |
@@ -74,9 +74,9 @@ tests: | |||
cron: 8 8 29 2 * | |||
steps: | |||
allow_skip_on_success: true | |||
cluster_profile: aws-autorelease-qe | |||
cluster_profile: aws-sustaining-autorelease-412 |
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.
4.14 use profile 412. Is it expected ?
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.
@yash2189 can you take a look
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.
Yes, this is expected . We decided to use the same profile for all the EUS release tests jobs.
Since, the actual account name for cloud accounts has the prefix 412, so we didn't want to update the cluster profile name and use it as is.
/lgtm cancel |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liangxia, rioliu-rh, yash2189 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 |
/pj-rehearse ack |
@yash2189: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
6924530
into
openshift:master
@yash2189: Updated the
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 PR adds the following changes
sustaining
aws,gcp,azure profiles