[
https://issues.jenkins-ci.org/browse/JENKINS-8562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=160275#comment-160275
]
Steven Aerts commented on JENKINS-8562:
---------------------------------------
This bug is probably a duplicate of #JENKINS-3265, I think.
> Reloading Hudson Configuration Causes "Duplicate" Gerrit Jobs To Trigger
> ------------------------------------------------------------------------
>
> Key: JENKINS-8562
> URL: https://issues.jenkins-ci.org/browse/JENKINS-8562
> Project: Jenkins
> Issue Type: Bug
> Components: gerrit-trigger
> Reporter: Cody Cutrer
> Assignee: rsandell
> Attachments: duplicates.png
>
>
> Repro steps:
> Create a job that is triggered by a gerrit event, and the build step is to
> sleep for 5 seconds (no need to actually configure the git plugin; we don't
> care to actually compile it). Save the job, and make sure it gets triggered
> by uploading a new change to gerrit. Then reload Hudson configuration from
> disk from the manage hudson menu, and upload another patchset to gerrit. The
> test job will run multiple times on different slave, with the same build
> number. Each time you reload configuration, another duplicate is added.
> After all the duplicates are complete, only the single build is recorded, but
> the console logs are all mixed together. Retriggering a build does not cause
> any duplication, but query for a patchset and triggering it that way does.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
