-
Improvement
-
Resolution: Fixed
-
Major
Currently we always load FlowExecution when loading a build even though we might not actually need it. This is thought to slow down some things, such as getBuildHealth, since we are loading executions for some historical completed builds and then not using them. The loading should be on demand only.
Since currently FlowExecution.onComplete is called soon thereafter, we would need some other marker in WorkflowRun for a completed build. Could check for logsToCopy == null though this is deleted in JENKINS-38381. Probably better to use completed as noted here.
- is duplicated by
-
JENKINS-47224 Pipeline builds failing/hanging under load: RejectedAccessException: Scripts not permitted to use staticMethod WorkflowScript ___cps___6009
- Closed
-
JENKINS-49086 Lazy-initialize FlowNodeStorage and heads, etc
- Closed
- is related to
-
JENKINS-47224 Pipeline builds failing/hanging under load: RejectedAccessException: Scripts not permitted to use staticMethod WorkflowScript ___cps___6009
- Closed
- relates to
-
JENKINS-50030 Job.getEstimatedDurationCandidates should not force loading of builds
- Open
-
JENKINS-49086 Lazy-initialize FlowNodeStorage and heads, etc
- Closed
- links to