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

JIRA plugin shouldn't fail build if a JIRA issue doesn't exist

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • plugin-proposals
    • None
    • Platform: All, OS: All

      It seems that the JIRA plugin resolves anything like "\s*-\d*" as a
      jira bug number. A common string that fits this pattern is UTF-8,
      which likely isn't a jira bug number. We've had a few builds fail because the
      plugin failed to add a comment to the non-existent UTF-8 Jira bug
      after a successful build.

      More generally, perhaps the plugin can distinguish between issues that exist and
      issues that don't. In other words, a typo in a commit message
      shouldn't cause the build to fail.

          [JENKINS-548] JIRA plugin shouldn't fail build if a JIRA issue doesn't exist

          I believe this is now fixed in the JIRA plugin 1.3.

          Kohsuke Kawaguchi added a comment - I believe this is now fixed in the JIRA plugin 1.3.

          Hudson now talks to JIRA and obtains the list of valid project prefixes. So as
          long as you won't have the 'UTF' project, it shouldn't consider 'UTF-8' as an
          issue anymore.

          Kohsuke Kawaguchi added a comment - Hudson now talks to JIRA and obtains the list of valid project prefixes. So as long as you won't have the 'UTF' project, it shouldn't consider 'UTF-8' as an issue anymore.

            Unassigned Unassigned
            nidaley nidaley
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: