Bulk frequency reduce of 4.12 periodics to limit costs of CI platform #40924
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
openshift-ci
bot
added
the
approved
openshift-merge-robot
added
the
needs-rebase
|
/lgtm |
Signed-off-by: Jakub Guzik <jguzik@redhat.com>
Signed-off-by: Jakub Guzik <jguzik@redhat.com>
openshift-merge-robot
removed
the
needs-rebase
|
[REHEARSALNOTIFIER]
A total of 177 jobs have been affected by this change. The above listing is non-exhaustive and limited to 35 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 ack |
openshift-ci-robot
added
the
rehearsals-ack
|
/lgtm |
|
@jmguzik: all tests passed! Full PR test history. Your PR dashboard. 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. I understand the commands that are listed here. |
|
@jmguzik: Updated the following 8 configmaps:
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/test-infra repository. |
wking
added a commit
to wking/openshift-release
that referenced
this pull request
Aug 13, 2023
…every 48h Rolling back changes from 26ebda9 (Bulk frequency reduce of 4.12 periodics to limit costs of CI platform, 2023-07-07, openshift#40924) and similar. These jobs are very cheap, because they do not launch a cluster (they just compare release image content), and running them more frequently gives plenty of post-merge time before a release gets cut to discuss what to do about changes like [1] adding route53:ListTagsForResources as an ingress permission in 4.12. [1]: openshift/cluster-ingress-operator#954
openshift-merge-robot
pushed a commit
that referenced
this pull request
Aug 15, 2023
…every 48h (#42215) Rolling back changes from 26ebda9 (Bulk frequency reduce of 4.12 periodics to limit costs of CI platform, 2023-07-07, #40924) and similar. These jobs are very cheap, because they do not launch a cluster (they just compare release image content), and running them more frequently gives plenty of post-merge time before a release gets cut to discuss what to do about changes like [1] adding route53:ListTagsForResources as an ingress permission in 4.12. [1]: openshift/cluster-ingress-operator#954
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you were affected and think it's a mistake either revert new value or contact us on #forum-testplatform