Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-13500

Jira plugin post "integrated in" comment on every build

    XMLWordPrintable

Details

    Description

      An "Integrated in build XYZ" comment is added for every build of a job when no svn changes of the specific issue was detected.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-17156 If Updater fails to update due to missing permission, it crashes and never flushes the comment queue

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            Ascending order - Click to sort in descending order
            ricktw Rick Oosterholt added a comment -

            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:

            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.]

            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.

            ricktw Rick Oosterholt added a comment - 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: 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.] 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.
            jminne jminne added a comment -

            This may be a duplicate

            jminne jminne added a comment - This may be a duplicate
            krulls Stephan Krull added a comment -

            This bug is considered in https://github.com/jenkinsci/jira-plugin/pull/50 and definitily a duplicate of JENKINS-17156 (hence should be closed).

            krulls Stephan Krull added a comment - This bug is considered in https://github.com/jenkinsci/jira-plugin/pull/50 and definitily a duplicate of JENKINS-17156 (hence should be closed).
            warden Radek Antoniuk added a comment -

            Closing as duplicate of JENKINS-17156

            warden Radek Antoniuk added a comment - Closing as duplicate of JENKINS-17156

            People

              Unassigned Unassigned
              ricktw Rick Oosterholt
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: