jenkinsci / jenkinsci/workflow-basic-steps-plugin
[JENKINS-47786] add name field to timeout
- Lingua principale
- Java
- Stelle
- 73
- Fork
- 129
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
we use nested timeouts. Would be nice to print not only timeout, but their names into the log:
instead of:
2017-10-29 11:24:43 Timeout set to expire in 2 hr 0 min
[Pipeline] timeout
[Pipeline] // timeout
2017-10-29 11:30:28 Cancelling nested steps due to timeout
would be better:
2017-10-29 11:24:43 Timeout set to expire in 2 hr 0 min
[Pipeline] timeout
[Pipeline] // timeout
2017-10-29 11:30:28 Cancelling nested steps due to timeout
or something similar
---
Originally reported by pan64, imported from: add name field to timeout
Raw content of original issue
we use nested timeouts. Would be nice to print not only timeout, but their names into the log:
instead of:
2017-10-29 11:24:43 Timeout set to expire in 2 hr 0 min
[Pipeline] timeout
[Pipeline] // timeout
2017-10-29 11:30:28 Cancelling nested steps due to timeout
would be better:
2017-10-29 11:24:43 Timeout <name> set to expire in 2 hr 0 min
[Pipeline] timeout <name>
[Pipeline] // timeout <name>
2017-10-29 11:30:28 Cancelling nested steps due to timeout <name>or something similar
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Start by locating the timeout step and the existing log messages in the workflow-basic-steps-plugin, then trace how nested Pipeline timeouts are represented. Update the timeout-related output so the configured name is included consistently, and verify the resulting logs for nested timeouts match the requested behavior.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java
- Ambito
- ci-cd
- Tipo di issue
- Funzionalità
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 45/100