jenkinsci / jenkinsci/workflow-basic-steps-plugin
Allow (declarative) pipeline timeout's to mark builds as failed instead of aborted
- Lingua principale
- Java
- Stelle
- 73
- Fork
- 129
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
### What feature do you want to see added?
Add an option to the Timeout option to allow setting what status the build should have if it times out.
Currently the timeout option in the Declarative pipeline will not mark a build as failed if it's "triggered", and instead aborts it. This results in the build health (icon) not being affected, and no mail being sent out due to the failure.
This makes it easy to miss builds that fail due to the timeout.
And from what I can tell there is no (easy) way to make the timeout mark a build as failed instead of aborted.
This was changed in the timeout plugin some years back from what I can tell:
https://issues.jenkins.io/browse/JENKINS-9203
https://issues.jenkins.io/browse/JENKINS-9548
And maybe this is relevant?:
https://issues.jenkins.io/browse/JENKINS-55295
### Upstream changes
_No response_
### Are you interested in contributing this feature?
_No response_
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start by tracing the Declarative Pipeline Timeout option and reviewing JENKINS-9203, JENKINS-9548, and JENKINS-55295. Define how timeout outcomes should affect build status, health, and notifications, then add coverage for the selected status behavior.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java
- Ambito
- ci-cd
- Tipo di issue
- Funzionalità
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Attiva
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 45/100