|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

I've been looking at this, and made a change that appears to fix the problem.
I added a new method getGerritEventListenerName to GerritEventListener. I then implemented this in GerritTrigger to return the name of the job. Then in GerritHandler#addListener I can check to see if the same job is already in the gerritEventListeners set. This appears to solve the problem but is it a reasonable approach?
I am also unsure if I should be removing the old listener and adding the new one, or simply not adding the new listener.