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

One bad issue stops all other issues from being updated

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • jira-plugin
    • None

      The jenkins plugin updates Jira Tickets with a link back to the jenkins build job that included the code change.

      If someone commits to SVN with an invalid JT#(i.e. SPP-123456 where 123456 does not exist), then the other JT that are included in that job's changeset will not be updated with links to the build job.

      The build job does not fail when this error occurs, and that is good.

      The desired behavior is:
      1) update all the other valid JT referenced in the job's changeset.

      2) It would be nice if an email was sent to the mailing list. Or even better, if an email was sent to the user who did the bad commit comment.

      When this happens, the console output says:
      18:35:18 Error updating JIRA issues. Saving issues for next build.
      18:35:18 com.atlassian.jira.rpc.exception.RemotePermissionException: This issue does not exist or you don't have permission to view it.

      But in fact, the other issues are not updated on the next build.

            Unassigned Unassigned
            jminne jminne
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: