Support pipeline count #29
Assignees
Comments
gbenhaim
added a commit
that referenced
this issue
May 11, 2025
1. Add special resource to the Workload created for a PipelinRun. The resource will be used for controlling the amount of concurrent PipelineRuns that can be executed at the same time. 2. Remove the default 1GB memory request, since it's not needed after the addition of the new resource request. 3. Tests refactoring for sharing assertion and making them more informative. closes: #29 Signed-off-by: Gal Ben Haim <[email protected]>
gbenhaim
added a commit
that referenced
this issue
May 11, 2025
1. Add special resource to the Workload created for a PipelinRun. The resource will be used for controlling the amount of concurrent PipelineRuns that can be executed at the same time. 2. Remove the default 1GB memory request, since it's not needed after the addition of the new resource request. 3. Tests refactoring for sharing assertion and making them more informative. closes: #29 Signed-off-by: Gal Ben Haim <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In the function which generate the PodSpec, add a resource for tracking the number of pipeline runs.
The name of the resource should be
tekton.dev/pipelinerunsand its value should be hardcoded to 1.By doing that, we can allow users to limit the number of running pipelines.
The text was updated successfully, but these errors were encountered: