ci-operator/config/openshift/release: Run credentials-request-freeze every 48h #42215
Conversation
openshift-ci
bot
added
the
approved
…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
wking
force-pushed
the
frequent-cred-freeze-runs
branch
from
e1b4403 to
d2d6640
Compare
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
Nothing to rehearse; I'm just adjusting the interval. /pj-rehearse ack |
|
/lgtm |
|
/pj-rehearse ack |
openshift-ci-robot
added
the
rehearsals-ack
|
/lgtm |
|
prow likes rehearsal ack but not lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: patrickdillon, wking 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 |
1 similar comment
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: patrickdillon, wking 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 |
|
@wking: all tests passed! 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. |
4 participants
Rolling back changes from 26ebda9 (#40924) and similar, CC @jmguzik.
credentials-request-freezejobs 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 openshift/cluster-ingress-operator#954 addingroute53:ListTagsForResourcesas an ingress permission in 4.12.