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

Email-ext: Fixed email is sent if build goes from unstable to unstable

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • email-ext-plugin
    • None
    • Platform: All, OS: All

    Description

      This is for the email-ext plugin.

      Ive configured a job to send an email to a global notification list, if the
      build fails or if it has been fixed.

      If the last build was unstable and the new build is also unstable then I receive
      an email stating that the build has been fixed. As both builds were unstable I
      dont expect an email to be sent out stating that the build was fixed.

      Attachments

        Activity

          Code changed in hudson
          User: : ashlux
          Path:
          trunk/hudson/plugins/email-ext/src/main/java/hudson/plugins/emailext/plugins/content/BuildStatusContent.java
          https://hudson.dev.java.net/source/browse/hudson/trunk/hudson/plugins/email-ext/src/main/java/hudson/plugins/emailext/plugins/content/BuildStatusContent.java?view=diff&rev=26119&p1=trunk/hudson/plugins/email-ext/src/main/java/hudson/plugins/emailext/plugins/content/BuildStatusContent.java&p2=trunk/hudson/plugins/email-ext/src/main/java/hudson/plugins/emailext/plugins/content/BuildStatusContent.java&r1=26118&r2=26119
          trunk/hudson/plugins/email-ext/src/test/java/hudson/plugins/emailext/plugins/content/BuildStatusContentTest.java
          https://hudson.dev.java.net/source/browse/hudson/trunk/hudson/plugins/email-ext/src/test/java/hudson/plugins/emailext/plugins/content/BuildStatusContentTest.java?view=auto&rev=26119
          http://jenkins-ci.org/commit/26119
          Log:
          [FIXED JENKINS-953] When the pre-build trigger is used with $BUILD_STATUS, the status is incorrectly reported as successful or fixed. Reporting the build's status as "fixed", "success", etc. doesn't make sense when the build is still building.

          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in hudson User: : ashlux Path: trunk/hudson/plugins/email-ext/src/main/java/hudson/plugins/emailext/plugins/content/BuildStatusContent.java https://hudson.dev.java.net/source/browse/hudson/trunk/hudson/plugins/email-ext/src/main/java/hudson/plugins/emailext/plugins/content/BuildStatusContent.java?view=diff&rev=26119&p1=trunk/hudson/plugins/email-ext/src/main/java/hudson/plugins/emailext/plugins/content/BuildStatusContent.java&p2=trunk/hudson/plugins/email-ext/src/main/java/hudson/plugins/emailext/plugins/content/BuildStatusContent.java&r1=26118&r2=26119 trunk/hudson/plugins/email-ext/src/test/java/hudson/plugins/emailext/plugins/content/BuildStatusContentTest.java https://hudson.dev.java.net/source/browse/hudson/trunk/hudson/plugins/email-ext/src/test/java/hudson/plugins/emailext/plugins/content/BuildStatusContentTest.java?view=auto&rev=26119 http://jenkins-ci.org/commit/26119 Log: [FIXED JENKINS-953] When the pre-build trigger is used with $BUILD_STATUS, the status is incorrectly reported as successful or fixed. Reporting the build's status as "fixed", "success", etc. doesn't make sense when the build is still building.
          ashlux ashlux added a comment -

          I couldn't reproduce this, at least as a unit test.

          ashlux ashlux added a comment - I couldn't reproduce this, at least as a unit test.
          mindless Alan Harder added a comment -

          Will close soon without further input, thanks.

          mindless Alan Harder added a comment - Will close soon without further input, thanks.
          mindless Alan Harder added a comment -

          Is this old issue still a problem?

          mindless Alan Harder added a comment - Is this old issue still a problem?
          redsolo redsolo added a comment -

          I guess part of the problem is the way the email-ext plugin is adding itself to
          the publisher list:
          BuildStep.PUBLISHERS.add(ExtendedEmailPublisher.DESCRIPTOR);

          I think fixing this issue would only require changing it to,
          BuildStep.PUBLISHERS.addNotifier(ExtendedEmailPublisher.DESCRIPTOR);

          redsolo redsolo added a comment - I guess part of the problem is the way the email-ext plugin is adding itself to the publisher list: BuildStep.PUBLISHERS.add(ExtendedEmailPublisher.DESCRIPTOR); I think fixing this issue would only require changing it to, BuildStep.PUBLISHERS.addNotifier(ExtendedEmailPublisher.DESCRIPTOR);
          dwdyer dwdyer added a comment -

          I see this too, with failed -> failed, when I have problems with ISSUE#949.

          The Ant build completes successfully but the Cobertura plugin reporting fails,
          so the build is marked as failed. If the same thing happens next time, I get
          an e-mail saying the "build is back to normal", but nothing has changed and the
          latest build is still marked as a failure.

          dwdyer dwdyer added a comment - I see this too, with failed -> failed, when I have problems with ISSUE#949. The Ant build completes successfully but the Cobertura plugin reporting fails, so the build is marked as failed. If the same thing happens next time, I get an e-mail saying the "build is back to normal", but nothing has changed and the latest build is still marked as a failure.
          redsolo redsolo added a comment -

          I assigned it to myself for no good reason.

          redsolo redsolo added a comment - I assigned it to myself for no good reason.

          People

            ashlux ashlux
            redsolo redsolo
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: