jenkinsci / jenkinsci/workflow-basic-steps-plugin
Allow (declarative) pipeline timeout's to mark builds as failed instead of aborted
- Lenguaje dominante
- Java
- Estrellas
- 73
- Forks
- 129
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
### 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_
Guía de contribución
Línea de trabajo
Comienza rastreando la opción Declarative Pipeline Timeout y revisando JENKINS-9203, JENKINS-9548 y JENKINS-55295. Define cómo deberían afectar los resultados de los timeouts al estado de la compilación, la salud y las notificaciones, y añade cobertura para el comportamiento de estado seleccionado.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- java
- Área
- ci-cd
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Activo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100