-
Bug
-
Resolution: Unresolved
-
Minor
In "performance-optimized" mode, Pipelines should only be persisting the Run a couple times (mostly at the start, finish, and when pausing or restarting) – that's part of what "optimized" means.
Instead a notify call is causing this to happen multiple times.
- is blocked by
-
JENKINS-50199 Failed pipeline jobs stuck running after incorrect resume
- Resolved
- links to