-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
update aws frequency #54056
update aws frequency #54056
Conversation
Looks good, but will let Andrew do review for day/time distribution |
3ae9e64
to
2458561
Compare
@afcollins PTAL |
...ci/openshift-qe-ocp-qe-perfscale-ci-main__aws-4.17-nightly-x86-loaded-upgrade-from-4.16.yaml
Outdated
Show resolved
Hide resolved
...ci/openshift-qe-ocp-qe-perfscale-ci-main__aws-4.17-nightly-x86-loaded-upgrade-from-4.16.yaml
Show resolved
Hide resolved
...hift-qe/ocp-qe-perfscale-ci/openshift-qe-ocp-qe-perfscale-ci-main__aws-4.16-nightly-x86.yaml
Outdated
Show resolved
Hide resolved
...hift-qe/ocp-qe-perfscale-ci/openshift-qe-ocp-qe-perfscale-ci-main__aws-4.14-nightly-x86.yaml
Outdated
Show resolved
Hide resolved
...ci/openshift-qe-ocp-qe-perfscale-ci-main__aws-4.16-nightly-x86-loaded-upgrade-from-4.15.yaml
Outdated
Show resolved
Hide resolved
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.
Checked them all. Couple of comments
2458561
to
16b06a9
Compare
@afcollins I updated according to your comments. |
16b06a9
to
869ff38
Compare
...hift-qe/ocp-qe-perfscale-ci/openshift-qe-ocp-qe-perfscale-ci-main__aws-4.13-nightly-x86.yaml
Outdated
Show resolved
Hide resolved
...hift-qe/ocp-qe-perfscale-ci/openshift-qe-ocp-qe-perfscale-ci-main__aws-4.14-nightly-x86.yaml
Outdated
Show resolved
Hide resolved
...hift-qe/ocp-qe-perfscale-ci/openshift-qe-ocp-qe-perfscale-ci-main__aws-4.14-nightly-x86.yaml
Outdated
Show resolved
Hide resolved
869ff38
to
f2d8154
Compare
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
@afcollins I updated according to your last 3 comments, and did not do any other new change, please have a review, thank you so much! Hopefully we are good to go! |
/pj-rehearse ack |
@qiliRedHat: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
workflow: openshift-qe-upgrade | ||
timeout: 8h0m0s | ||
- as: loaded-upgrade-416to417-252nodes | ||
cron: 0 6 24 * * |
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.
I am not crazy about this one running (which would take ~6 hours) and then loaded-upgrade-415to416-24nodes
starting at 9a on the same day.
Generally any 252 node runs we may want to block an exclusive window. But, we may also be fine. Will merge for now and adjust if required.
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
Thank you, @qiliRedHat !! Appreciate your diligence and initiative on this.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: afcollins, qiliRedHat 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 |
c94c3c6
into
openshift:master
Updated the frequency after 4.16 GA to doc https://docs.google.com/document/d/1NbXwfZwSkMdftuKW1Ob705rQk-XHLtPtP1d1vuqF9Vo. According to the doc.
Loaded-upgrade