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

email-ext regression trigger not firing when it should

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I apologize in advance, because I can't imagine this isn't my problem.

      I have a simple project, the builds triggered successfully by a subversion callback. When an additional JUnit test fails, the "regression" trigger isn't fired.

      I attach screenshots of my email-ext config, the build info screen showing that the number of fails is "+1", and a screenshot of the console output from the build, showing that there was a fail, but "No emails were triggered."

      i'm sure i'm missing something very simple, but i've been staring at this for a while. i'd appreciate any help. thanks!

        Attachments

        1. ScreenShot011.png
          ScreenShot011.png
          48 kB
        2. ScreenShot012.png
          ScreenShot012.png
          5 kB
        3. ScreenShot013.png
          ScreenShot013.png
          54 kB

          Activity

          Hide
          slide_o_mix Alex Earl added a comment -

          There wouldn't be any workarounds...there seems to be a code issue.

          Show
          slide_o_mix Alex Earl added a comment - There wouldn't be any workarounds...there seems to be a code issue.
          Hide
          fanhaf Michał Guminiak added a comment -

          I would also like to suggest that if one test is fixed and another is broken between builds it should still count as a regression I guess...

          Maybe we could check if there is a failing test with age 1 and then trigger the regression email?

          Show
          fanhaf Michał Guminiak added a comment - I would also like to suggest that if one test is fixed and another is broken between builds it should still count as a regression I guess... Maybe we could check if there is a failing test with age 1 and then trigger the regression email?
          Hide
          slide_o_mix Alex Earl added a comment -

          If you are familiar with Java, you could fork the plugin on GitHub, make and test the changes and issue a pull request. It may get done sooner that way

          Show
          slide_o_mix Alex Earl added a comment - If you are familiar with Java, you could fork the plugin on GitHub, make and test the changes and issue a pull request. It may get done sooner that way
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Alex Earl
          Path:
          src/main/java/hudson/plugins/emailext/plugins/EmailTrigger.java
          http://jenkins-ci.org/commit/email-ext-plugin/52dae3a93c5acb1a8e0a8f3149c49a5a2c4abc2e
          Log:
          Fix JENKINS-16404

          Added a check for the value of getFailCount if the child
          reports did not have any fails.

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/EmailTrigger.java http://jenkins-ci.org/commit/email-ext-plugin/52dae3a93c5acb1a8e0a8f3149c49a5a2c4abc2e Log: Fix JENKINS-16404 Added a check for the value of getFailCount if the child reports did not have any fails. –
          Hide
          slide_o_mix Alex Earl added a comment -

          Added check of getFailCount if the child reports don't have fails

          Show
          slide_o_mix Alex Earl added a comment - Added check of getFailCount if the child reports don't have fails

            People

            • Assignee:
              slide_o_mix Alex Earl
              Reporter:
              lcgerke lcgerke gerke
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: