-
New Feature
-
Resolution: Duplicate
-
Minor
-
None
I would like to edit the event executed when timeout is reach.
In some scenario, the event "Send interrupt signal to process" won't kill the running process. If I could catch some event, I could force the process to stop and for instance rollback environment.
timeout(5, unit:'MINUTES') { // 10 minutes process } catch { // specific timeout signal }
- duplicates
-
JENKINS-38769 Pipeline job hangs when agent loses network connectivity
-
- Resolved
-
-
JENKINS-25623 timeout step should be able to kill infinite loop
-
- Resolved
-
-
JENKINS-39072 timeout step should include more logging/diagnostics information
-
- Resolved
-
- is related to
-
JENKINS-35677 build-timeout-plugin cannot be used with pipelines (workflows)
-
- Resolved
-
-
JENKINS-32986 hard killing a pipeline leaves the JVM CPS thread running.
-
- Open
-
[JENKINS-32228] Event when timeout is reach should be customizable
Summary | Original: Timeout event should be customizable | New: Event when timeout is reach should be customizable |
Workflow | Original: JNJira [ 167812 ] | New: JNJira + In-Review [ 182853 ] |
Component/s | New: pipeline-general [ 21692 ] |
Component/s | Original: workflow-plugin [ 18820 ] |
Component/s | New: workflow-basic-steps-plugin [ 21712 ] | |
Component/s | Original: pipeline [ 21692 ] |
Component/s | New: durable-task-plugin [ 18622 ] |
Component/s | New: workflow-durable-task-step-plugin [ 21715 ] | |
Component/s | Original: durable-task-plugin [ 18622 ] |
Link | New: This issue is related to JENKINS-32986 [ JENKINS-32986 ] |
Link |
New:
This issue is related to |
Link |
New:
This issue duplicates |
Link |
New:
This issue duplicates |
Link |
New:
This issue duplicates |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |