[JIRA] (JENKINS-51002) Quiet period for parameterized pipeline job not working fully
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-51002 Quiet period for parameterized pipeline job not working fully Change By: Andrew Bayer Component/s: workflow-job-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51002) Quiet period for parameterized pipeline job not working fully
Title: Message Title Christian Göller created an issue Jenkins / JENKINS-51002 Quiet period for parameterized pipeline job not working fully Issue Type: Bug Assignee: Unassigned Components: pipeline Created: 2018-04-25 15:14 Environment: Jenkins 2.117 runnig as docker container on Docker 18.03 on RHEL 7.4 Chrome 65 Priority: Minor Reporter: Christian Göller In my setup a build job triggers a deployment job using the build step All jobs are pipeline jobs. The deployment job has a quiet period of 10 minutes configured in the job. The deployment jobs is parameterized. The build job hands over the git commit hash and the artifact hash created in the build. When the deployment job is triggered, the quiet period is taken into account. So far everything is okay. When the build job triggers the deployment job a 2nd time, a new deployment job is scheduled with a fresh quiet period. The build queue contains now 2 jobs. The expected behaviour is: Only one deployment job is in the queue and the quiet period is reset. Some more information: The parameters of both triggered jobs are different.
