Send the "still unstable" email rather than the "unstable" email, when the previous status was fail, and the status before that was unstable.

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      I'm using the email-ext plugin, with both "unstable" and "still unstable" triggers defined.

      Tests are failing, so my builds are unstable. The "still unstable" email is sent.
      Someone commits a change that causes a compile error, the build fails. The "failed" email is sent.
      Someone commits a fix for the compile error, the build goes back to unstable.

      The problem is that at this point, the "unstable" email is sent. It should be the "still unstable" email, since before the previous fail, the status was unstable. If we send the "unstable" email, it gives the impression that new failures were introducted in that build, which is not the case.

            Assignee:
            farshidce
            Reporter:
            Matthew Webber
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: