ci-operator/config/openshift/release: Add 4.14 and 4.15 cred-freeze jobs#43564
ci-operator/config/openshift/release: Add 4.14 and 4.15 cred-freeze jobs#43564wking wants to merge 1 commit intoopenshift:masterfrom
Conversation
openshift-ci
Bot
added
the
approved
wking
force-pushed
the
credentials-requests-freeze-4.14
branch
from
40c5ea4 to
daf4f4a
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: 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 |
4.14, becasue we want to freeze these through the life of 4.14, following the existing pattern, most recently d666767 (ci-operator/config/openshift/release/openshift-release-master__nightly-4.13: Add oldest-* jobs, 2023-04-26, openshift#38728). I'm not pulling in the rollback job this time, because that's moving under QE and is in flight separately in [1]. I'm also adding a 4.15 cred-freeze job this time, to catch up with dbcbb85 (add explanation of blocking jobs in master before service streams, 2023-09-18, openshift#43418). As I pointed out in d666767, I'm still concerned about the amount of churn that I expect will land during the engineering candidate, but I'm not on the release-oversight team, and if they perfer having a blocker job in the development branch with occasional pin bumps, that's fine with me. The bulk of the ci-operator/jobs content is from: $ make jobs But then I manually edited to inject reporter_config, as described in 08db24d (ci-operator/jobs/openshift/release: Ping @Patch-Manager for cred-freeze failures, 2021-12-08, openshift#24177). [1]: openshift#43401
wking
force-pushed
the
credentials-requests-freeze-4.14
branch
from
daf4f4a to
d600e26
Compare
|
/pj-rehearse periodic-ci-openshift-release-master-nightly-4.14-credentials-request-freeze periodic-ci-openshift-release-master-nightly-4.15-credentials-request-freeze |
|
[REHEARSALNOTIFIER]
A total of 206 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 periodic-ci-openshift-release-master-nightly-4.15-credentials-request-freeze |
openshift-merge-robot
added
the
needs-rebase
|
PR needs rebase. 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. |
|
Issues in openshift/release go stale after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci
Bot
added
the
lifecycle/stale
|
@wking: 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. |
|
Stale issue in openshift/release rot after 15d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
openshift-ci
Bot
added
lifecycle/rotten
|
Rotten issues in openshift/release close after 15d of inactivity. Reopen the issue by commenting /close |
|
@openshift-bot: Closed this PR. 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. |
4 participants
4.14, becasue we want to freeze these through the life of 4.14, following the existing pattern, most recently d666767 (#38728). I'm not pulling in the rollback job this time, because that's moving under QE and is in flight separately in #43401.
I'm also adding a 4.15 cred-freeze job this time, to catch up with dbcbb85 (#43418). As I pointed out in d666767, I'm still concerned about the amount of churn that I expect will land during the engineering candidate, but I'm not on the release-oversight team, and if they perfer having a blocker job in the development branch with occasional pin bumps, that's fine with me.
The bulk of the ci-operator/jobs content is from:
$ make jobsBut then I manually edited to inject
reporter_config, as described in 08db24d (#24177).