-
New Feature
-
Resolution: Done
-
Major
-
-
Pipeline - October, Pipeline - December
As a user of pipeline, I WANNA GO FAST.
To do that, I'm okay with sacrificing some of the ability to resume a pipeline after a hard Jenkins crash, as long as it means pipelines run fast. It would be nice if I can still resume the pipeline after a clean/safe restart of the master, though!
This differs from https://issues.jenkins-ci.org/browse/JENKINS-30896 because for this we're sacrificing some of the guarantees pipeline normally provides.
Concrete needs:
- Implement storage engine (workflow-support)
- Implement options to select that storage engine (workflow-job)
- Implement ability to RUN that storage engine (workflow-cps)
- is blocked by
-
JENKINS-47172 Provide more granular control of pipeline flownode persistence
-
- Closed
-
- is related to
-
JENKINS-30896 Unoptimized node storage
-
- Closed
-
-
JENKINS-33761 Ability to disable Pipeline durability and "resume" build.
-
- Closed
-
- relates to
-
JENKINS-49086 Lazy-initialize FlowNodeStorage and heads, etc
-
- Closed
-
[JENKINS-47173] Offer a high-performance storage engine for pipeline at some cost to resumability
Epic Link | New: JENKINS-47170 [ 185575 ] |
Link |
New:
This issue is related to |
Link |
New:
This issue is related to |
Link |
New:
This issue is blocked by |
Issue Type | Original: Improvement [ 4 ] | New: New Feature [ 2 ] |
Sprint | New: Pipeline - October [ 406 ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Sprint | Original: Pipeline - October [ 406 ] | New: Pipeline - October, Pipeline - December [ 406, 446 ] |
Based on a discussion I had today, it may be helpful to have a Jenkins system property (or option) to control what the default storage engine and Durability Mode for pipeline are.