Status: Closed (View Workflow)
The "quiet period" option is not possible to be configured from the Declarative pipeline like "options" or "parameters".
Could be interesting to have that feature inside the declarative pipelines.
- is blocking
JENKINS-30519 Declarative job properties in multibranch
- relates to
JENKINS-37588 Multibranch pipeline does not allow quiet time or throttle
- links to
We could work around this in Declarative with a DeclarativeOption that results in setting the quiet period for the job...worth considering.
Isn't the use case of commits arriving in quick succession obsolete since Git and cloud agents?
Yes, I think so…on some rainy day I may propose an issue to deprecate the very concept of a quiet period in Jenkins core, and make it a plugin you can install for exotic use cases.
Nothing to do with Declarative vs. Scripted, only multibranch vs. standalone.