Prow: Increase max prowjob age to 24h #753
Conversation
Now that we trigger jenkins jobs through Prow, we have some jobs that can take more than 4h. Increasing to 24h. Signed-off-by: Lennart Jern <lennart.jern@est.tech>
metal3-io-bot
added
the
size/XS
|
/approve |
|
/override metal3-ubuntu-e2e-integration-test-main |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mboukhalfa 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 |
metal3-io-bot
added
the
approved
|
@lentzi90: Overrode contexts on behalf of lentzi90: metal3-ubuntu-e2e-integration-test-main 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. |
|
@lentzi90: 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/test-infra repository. |
|
Indeed :( I also see it on metal3-io/baremetal-operator#1724 for https://jenkins.nordix.org/view/Metal3/job/metal3-bmo-e2e-test-optional-pull/68/ |
Now that we trigger jenkins jobs through Prow, we have some jobs that can take more than 4h. Increasing to 24h.
Edit: I suspect this may be why we have seen some jobs fail but report success (kubernetes-sigs/prow#142). If the prowjob was cleaned up, then what would the jenkins-operator do? 🤔