[
https://issues.jenkins-ci.org/browse/JENKINS-13500?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162249#comment-162249
]
ricktw commented on JENKINS-13500:
----------------------------------
Well,
I've found the cause of this strange behavior:
The plugin was trying to comment on an issue which does not have 'comments'
activated. In this case the plugin also logs:
{code}
Error updating JIRA issues. Saving issues for next build.
com.atlassian.jira.rpc.exception.RemoteException: Errors: {}
Error Messages: [Jenkins, you do not have the permission to comment on this
issue.]
{code}
which is a bit misleading because of the '... permission ...' part.
When this happens *all* detected Jira issues are stored to be registered in the
next build (JiraCarryOverAction), even the ones which already have been
processed.
This is why the "Integrated in" message is posted over-and-over-again.
I think only the issues which are not processed correctly should be stored in
'JiraCarryOverAction'.
ps. I think this issue also occurs when this plugin is trying to comment on
issues were commenting is activated but were the configured user does not have
access to.
> Jira plugin post "integrated in" comment on every build
> -------------------------------------------------------
>
> Key: JENKINS-13500
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13500
> Project: Jenkins
> Issue Type: Bug
> Components: jira
> Reporter: ricktw
>
> An "Integrated in build XYZ" comment is added for every build of a job when
> no svn changes of the specific issue was detected.
--
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
