-
Bug
-
Resolution: Done
-
Blocker
-
Pipelines 1.14.1
-
4
-
False
-
-
False
-
Pipelines as Code watcher would get stuck when using a concurrency setting with a max-keep-run annotations. It now avoid trying to cleanup the PipelineRuns that are in a Pending state
-
-
-
Pipelines Sprint 259
Description of problem:
when using max-keep-run and pipelines-as-code concurrency, the watcher would try to deleted the Pending PipelineRun when it should skip it.
Prerequisites (if any, like setup, operators/versions):
Steps to Reproduce
Create a lot of PipelineRun via PAC with a max-keep-run annotation on the PipelineRun and see that the watcher is getting "stuck" and not able to process the Pending PipelineRun.
Actual results:
Expected results:
Reproducibility (Always/Intermittent/Only Once):
Acceptance criteria:
Definition of Done:
Build Details:
Additional info (Such as Logs, Screenshots, etc):