jenkinsci / jenkinsci/branch-api-plugin
[JENKINS-37588] Multibranch pipeline does not allow quiet time or throttle
- Dominant language
- Java
- Stars
- 39
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
Currently, for an individual pipeline job I can set a quiet time to avoid one-for-one commit-to-build ratio when there are many commits in a short time. I like to use the multibranch plugin to allow branch automation, but there does not appear to be a way for a multibranch config (either the meta-job itself or from within a Jenkinsfile) to define a quiet time or some other ability to throttle job runs.
---
Originally reported by bsipos, imported from: Multibranch pipeline does not allow quiet time or throttle
Raw content of original issue
Currently, for an individual pipeline job I can set a quiet time to avoid one-for-one commit-to-build ratio when there are many commits in a short time. I like to use the multibranch plugin to allow branch automation, but there does not appear to be a way for a multibranch config (either the meta-job itself or from within a Jenkinsfile) to define a quiet time or some other ability to throttle job runs.
- environment:
Running jenkins 2.15 with pipeline-multibranch 2.8.
Contributor guide
Research direction
Start by reviewing the branch-api-plugin implementation and how quiet time is configured for individual pipeline jobs. Compare the multibranch configuration and Jenkinsfile options described in the issue, then define whether throttling belongs in the meta-job, the Jenkinsfile, or both. Done means multibranch pipelines can configure quiet time or an equivalent run-throttling behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100