-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
PipelineRun concurrency control
-
False
-
False
-
To Do
-
SECFLOWOTL-244 - Advanced pipelinerun concurrency control
-
100% To Do, 0% In Progress, 0% Done
-
Undefined
Goal
As a cluster-admin, I want to set max concurrent pipelineruns allowed to run on the platform. PipelineRuns scheduled after reaching the max concurrent number, should either get queued or get cancelled depending on a global configuration.
Acceptance Criteria
- Admin can set max concurrent pipelineruns at the cluster level
- Admin can configure queueing or cancellation when max concurrent pipelinerun number is reached
Related Work
- is blocked by
-
SRVKP-1669 R&D PipelineRun concurrency control
-
- To Do
-
-
SRVKP-8728 Testing for the epic
-
- To Do
-
- relates to
-
SRVKP-1547 Pipeline-as-code concurrency control
-
- Closed
-
-
RHDEVDOCS-4720 PAC: Pipeline-as-code concurrency control
-
- Closed
-