Details
-
Type:
New Feature
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Component/s: workflow-api-plugin, workflow-cps-plugin, workflow-job-plugin
-
Labels:
-
Similar Issues:
-
Epic Link:
-
Sprint:Blue Ocean 1.4 - beta 2, Pipeline - December
Description
Having some state being generated at the each node during execution, resuming builds after jenkins restarts or nodes reboots are just not feasible sometimes and can result in infinite hangs in some cases. Also, providing durability results in extensive writes to disk that can bring performance crashing down.
It would be great to be able to specify that jobs don't resume upon interruptions, but rather just fail. This would increase the robustness of the system ideally, since upon nodes restarting, they quickly pick up jobs that tries to resume and hangs exhausting all available executors quickly.
Implementation notes:
- Requires a new OptionalJobProperty on the job, optionally a new BranchProperty in workflow-multibranch-plugin that echoes that same property
- Needs some way to signal to storage (workflow-support) and execution (workflow-cps) that the pipeline is running with resume OFF to hint that they can use faster nondurable execution.
Attachments
Issue Links
- is blocked by
-
JENKINS-49961 NPE from CpsFlowExecution.saveOwner
-
- Resolved
-
- is duplicated by
-
JENKINS-37475 Add a configurable switch on job that causes CPS to silently not continue on non-serializable code
-
- Resolved
-
- is related to
-
JENKINS-28183 Hard killed job's stage blocks stage in following jobs
-
- Resolved
-
-
JENKINS-45917 [Jenkins v2.63] Build queue deadlocks
-
- Closed
-
-
JENKINS-47173 Offer a high-performance storage engine for pipeline at some cost to resumability
-
- Closed
-
-
JENKINS-47390 Allow durable task step to, uh, not be. Durable, that is.
-
- Open
-
- relates to
-
JENKINS-36013 Automatically abort ExecutorPickle rehydration from an ephemeral node
-
- Closed
-
-
JENKINS-49079 Copy job properties for new branch project from base/default branch
-
- Open
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link | JENKINS-35399 [ 171192 ] |
Link |
This issue is related to |
Workflow | JNJira [ 169740 ] | JNJira + In-Review [ 183632 ] |
Component/s | pipeline-general [ 21692 ] |
Component/s | workflow-plugin [ 18820 ] |
Component/s | workflow-job-plugin [ 21716 ] | |
Component/s | pipeline [ 21692 ] |
Component/s | workflow-cps-plugin [ 21713 ] |
Issue Type | Improvement [ 4 ] | New Feature [ 2 ] |
Link |
This issue is duplicated by |
Link |
This issue relates to |
Attachment | Screen Shot 2017-07-19 at 11.14.33 AM.png [ 38963 ] |
Attachment | Screen Shot 2017-07-19 at 11.14.33 AM.png [ 38963 ] |
Link |
This issue is related to |
Assignee | Jesse Glick [ jglick ] |
Assignee | Sam Van Oort [ svanoort ] |
Summary | Ability to disable "resume" build. | Ability to disable Pipeline durability and "resume" build. |
Description |
Having some state being generated at the each node during execution, resuming builds after jenkins restarts or nodes reboots are just not feasible sometimes. I've also never ever seen it work correctly, each time a job tries to resume it hangs infinitely and I always have to go in and kill the job manually. It would be great to be able to specify that jobs don't resume upon interruptions, but rather just fail. This would increase the robustness of the system ideally, since upon nodes restarting, they quickly pick up jobs that tries to resume and hangs exhausting all available executors quickly. |
Having some state being generated at the each node during execution, resuming builds after jenkins restarts or nodes reboots are just not feasible sometimes and can result in infinite hangs in some cases. Also, providing durability results in extensive writes to disk that can bring performance crashing done. It would be great to be able to specify that jobs don't resume upon interruptions, but rather just fail. This would increase the robustness of the system ideally, since upon nodes restarting, they quickly pick up jobs that tries to resume and hangs exhausting all available executors quickly. |
Component/s | blueocean-plugin [ 21481 ] |
Sprint | Blue Ocean 1.3 - candidates [ 326 ] |
Epic Link | JENKINS-35399 [ 171192 ] | JENKINS-47170 [ 185575 ] |
Component/s | blueocean-plugin [ 21481 ] |
Link |
This issue is related to |
Description |
Having some state being generated at the each node during execution, resuming builds after jenkins restarts or nodes reboots are just not feasible sometimes and can result in infinite hangs in some cases. Also, providing durability results in extensive writes to disk that can bring performance crashing done. It would be great to be able to specify that jobs don't resume upon interruptions, but rather just fail. This would increase the robustness of the system ideally, since upon nodes restarting, they quickly pick up jobs that tries to resume and hangs exhausting all available executors quickly. |
Having some state being generated at the each node during execution, resuming builds after jenkins restarts or nodes reboots are just not feasible sometimes and can result in infinite hangs in some cases. Also, providing durability results in extensive writes to disk that can bring performance crashing done. It would be great to be able to specify that jobs don't resume upon interruptions, but rather just fail. This would increase the robustness of the system ideally, since upon nodes restarting, they quickly pick up jobs that tries to resume and hangs exhausting all available executors quickly. Implementation notes: * Requires a new OptionalJobProperty on the job, plus a new BranchProperty in branch-api-plugin that echoes that |
Description |
Having some state being generated at the each node during execution, resuming builds after jenkins restarts or nodes reboots are just not feasible sometimes and can result in infinite hangs in some cases. Also, providing durability results in extensive writes to disk that can bring performance crashing done. It would be great to be able to specify that jobs don't resume upon interruptions, but rather just fail. This would increase the robustness of the system ideally, since upon nodes restarting, they quickly pick up jobs that tries to resume and hangs exhausting all available executors quickly. Implementation notes: * Requires a new OptionalJobProperty on the job, plus a new BranchProperty in branch-api-plugin that echoes that |
Having some state being generated at the each node during execution, resuming builds after jenkins restarts or nodes reboots are just not feasible sometimes and can result in infinite hangs in some cases. Also, providing durability results in extensive writes to disk that can bring performance crashing done. It would be great to be able to specify that jobs don't resume upon interruptions, but rather just fail. This would increase the robustness of the system ideally, since upon nodes restarting, they quickly pick up jobs that tries to resume and hangs exhausting all available executors quickly. Implementation notes: * Requires a new OptionalJobProperty on the job, plus a new BranchProperty in branch-api-plugin that echoes that * Needs some way to signal to storage (workflow-support) and execution (workflow-cps) that the pipeline is running with resume OFF to hint that they can use faster nondurable execution. |
Description |
Having some state being generated at the each node during execution, resuming builds after jenkins restarts or nodes reboots are just not feasible sometimes and can result in infinite hangs in some cases. Also, providing durability results in extensive writes to disk that can bring performance crashing done. It would be great to be able to specify that jobs don't resume upon interruptions, but rather just fail. This would increase the robustness of the system ideally, since upon nodes restarting, they quickly pick up jobs that tries to resume and hangs exhausting all available executors quickly. Implementation notes: * Requires a new OptionalJobProperty on the job, plus a new BranchProperty in branch-api-plugin that echoes that * Needs some way to signal to storage (workflow-support) and execution (workflow-cps) that the pipeline is running with resume OFF to hint that they can use faster nondurable execution. |
Having some state being generated at the each node during execution, resuming builds after jenkins restarts or nodes reboots are just not feasible sometimes and can result in infinite hangs in some cases. Also, providing durability results in extensive writes to disk that can bring performance crashing done. It would be great to be able to specify that jobs don't resume upon interruptions, but rather just fail. This would increase the robustness of the system ideally, since upon nodes restarting, they quickly pick up jobs that tries to resume and hangs exhausting all available executors quickly. Implementation notes: * Requires a new OptionalJobProperty on the job, optionally a new BranchProperty in workflow-multibranch-plugin that echoes that same property * Needs some way to signal to storage (workflow-support) and execution (workflow-cps) that the pipeline is running with resume OFF to hint that they can use faster nondurable execution. |
Status | Open [ 1 ] | In Progress [ 3 ] |
Component/s | workflow-api-plugin [ 21711 ] |
Description |
Having some state being generated at the each node during execution, resuming builds after jenkins restarts or nodes reboots are just not feasible sometimes and can result in infinite hangs in some cases. Also, providing durability results in extensive writes to disk that can bring performance crashing done. It would be great to be able to specify that jobs don't resume upon interruptions, but rather just fail. This would increase the robustness of the system ideally, since upon nodes restarting, they quickly pick up jobs that tries to resume and hangs exhausting all available executors quickly. Implementation notes: * Requires a new OptionalJobProperty on the job, optionally a new BranchProperty in workflow-multibranch-plugin that echoes that same property * Needs some way to signal to storage (workflow-support) and execution (workflow-cps) that the pipeline is running with resume OFF to hint that they can use faster nondurable execution. |
Having some state being generated at the each node during execution, resuming builds after jenkins restarts or nodes reboots are just not feasible sometimes and can result in infinite hangs in some cases. Also, providing durability results in extensive writes to disk that can bring performance crashing down. It would be great to be able to specify that jobs don't resume upon interruptions, but rather just fail. This would increase the robustness of the system ideally, since upon nodes restarting, they quickly pick up jobs that tries to resume and hangs exhausting all available executors quickly. Implementation notes: * Requires a new OptionalJobProperty on the job, optionally a new BranchProperty in workflow-multibranch-plugin that echoes that same property * Needs some way to signal to storage (workflow-support) and execution (workflow-cps) that the pipeline is running with resume OFF to hint that they can use faster nondurable execution. |
Component/s | workflow-durable-task-step-plugin [ 21715 ] |
Link | This issue is related to JENKINS-47390 [ JENKINS-47390 ] |
Component/s | workflow-durable-task-step-plugin [ 21715 ] |
Sprint | Blue Ocean 1.4 - beta 2 [ 326 ] | Blue Ocean 1.4 - beta 2, Pipeline - December [ 326, 446 ] |
Rank | Ranked lower |
Remote Link | This issue links to "CloudBees Internal CD-298 (Web Link)" [ 19061 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Remote Link | This issue links to "CloudBees Internal CD-390 (Web Link)" [ 19741 ] |
Link | This issue relates to JENKINS-49079 [ JENKINS-49079 ] |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Labels | project-cheetah |
Link |
This issue is blocked by |
Attachment | JENKINS-33671_thread_dump.txt [ 44546 ] |