[JENKINS-51227] Quiet period should be configured from declarative pipelines - Jenkins Jira

XML

Word

Printable

Details

Type: Improvement
Status: Closed (View Workflow)
Priority: Minor
Resolution: Fixed
Component/s: pipeline-model-definition-plugin
Labels:
None

Similar Issues:

Show

Description

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.

Attachments

Issue Links

is blocking

JENKINS-30519 Declarative job properties in multibranch

Resolved

relates to

JENKINS-37588 Multibranch pipeline does not allow quiet time or throttle

Reopened

links to

PR #283

Activity

Ascending order - Click to sort in descending order

Jesse Glick added a comment - 2018-05-09 19:15

Nothing to do with Declarative vs. Scripted, only multibranch vs. standalone.

Jesse Glick added a comment - 2018-05-09 19:15 Nothing to do with Declarative vs. Scripted, only multibranch vs. standalone.

Andrew Bayer added a comment - 2018-05-14 15:37

We could work around this in Declarative with a DeclarativeOption that results in setting the quiet period for the job...worth considering.

Andrew Bayer added a comment - 2018-05-14 15:37 We could work around this in Declarative with a DeclarativeOption that results in setting the quiet period for the job...worth considering.

Javier Raez added a comment - 2018-05-14 16:38

That should be enough Andrew, and great.

Javier Raez added a comment - 2018-05-14 16:38 That should be enough Andrew, and great.

Daniel Beck added a comment - 2018-05-20 13:36

Isn't the use case of commits arriving in quick succession obsolete since Git and cloud agents?

Daniel Beck added a comment - 2018-05-20 13:36 Isn't the use case of commits arriving in quick succession obsolete since Git and cloud agents?

Jesse Glick added a comment - 2018-06-05 23:29

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.

Jesse Glick added a comment - 2018-06-05 23:29 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.

Andrew Bayer added a comment - 2018-08-09 18:00

PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/283

Andrew Bayer added a comment - 2018-08-09 18:00 PR up at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/283

Andrew Bayer added a comment - 2018-08-29 12:40

will be in Declarative 1.3.2.

Andrew Bayer added a comment - 2018-08-29 12:40 will be in Declarative 1.3.2.

Liam Newman added a comment - 2019-10-23 03:21

Bulk closing resolved issues.

Liam Newman added a comment - 2019-10-23 03:21 Bulk closing resolved issues.