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

Plugin comments on subsequent successful builds

    XMLWordPrintable

Details

    Description

      My use case involves creating JIRA tickets for failed Jenkins builds, which the plugin handles correctly. However, when a subsequent build succeeds (and a comment is therefore posted to the ticket) the issue does not get closed, but instead is accumulating all further successful builds in comments.

      Is that the intended behavior?

      Is there a way to NOT create a comment when the build succeeds for the second time in a row?

      Thanks!

      Attachments

        Activity

          jaykah Jay Kah added a comment -

          Anyone?

          jaykah Jay Kah added a comment - Anyone?

          This is correct behavior. Currently repeated failures do not create a new issue but update the existing issue until the issue is closed.
          However it makes sense I guess to automatically resolve the issue when the build passes, is this what you mean?
          If yes, a PR implementing this in JiraCreateIssueNotifier will be more than welcome

          warden Radek Antoniuk added a comment - This is correct behavior. Currently repeated failures do not create a new issue but update the existing issue until the issue is closed. However it makes sense I guess to automatically resolve the issue when the build passes, is this what you mean? If yes, a PR implementing this in JiraCreateIssueNotifier will be more than welcome
          jaykah Jay Kah added a comment -

          Thanks warden ! Thought it was supposed to resolve it when it passes.

          jaykah Jay Kah added a comment - Thanks warden ! Thought it was supposed to resolve it when it passes.
          johno Johno Crawford added a comment - This was implemented as part of https://github.com/jenkinsci/jira-plugin/pull/112

          People

            warden Radek Antoniuk
            jaykah Jay Kah
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: