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

email-ext plugin blocks execution of the other publishers when recipienced box is empty

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • email-ext-plugin
    • email-ext 2.22
      jenkins 1.470

      When

      • recipients 1,2 are specified in Project Recipient List
      • and plugin has Advanced configuration (different recipients lists for Success/Failure builds)
      • and Recipient List for Failure case is empty
      • and Recipient List for Success case has recipients 3,4,5,6

      Observed in the case of Success build in version 2.20: mail messages was sent to 1,2,3,4,5,6
      === BEGIN LOG ===
      . . .
      Checked in "D:\workspace\BST\view\BST\SourceCode\wrapBSTPOCR\BuildBSTPOCR.ver" version "\main\10".
      Email was triggered for: Success
      Sending email for trigger: Success
      Sending email to: 1@samsung.com 2@samsung.com 3@samsung.com 4@samsung.com 5@samsung.com 6@samsung.com

      Deleting project workspace... done

      Triggering a new build of BST-to-IDRS #20
      Notifying upstream projects of job completion
      Finished: SUCCESS
      === END LOG ===

      Observed in the case of Success build in version 2.22: no messages are sent, besidess execution of the other publishes is not performed (workspace is not deleted, downstram build is not triggered).
      === BEGIN LOG ===
      Checked in "D:\workspace\BST\view\BST\SourceCode\wrapBSTPOCR\BuildBSTPOCR.ver" version "\main\11".
      Email was triggered for: Success
      Sending email for trigger: Success
      === END LOG ===

          [JENKINS-14224] email-ext plugin blocks execution of the other publishers when recipienced box is empty

          Sorry, why you can't just delete FAILURE case?

          Kanstantsin Shautsou added a comment - Sorry, why you can't just delete FAILURE case?

          Because, I need to inform recipients 1,2 in case of failure and recipients 1,2,3,4,5,6 in case of success.
          I rolled back email-ext to 2.20 temporary as a quick solution.

          Alexey Gavrilov added a comment - Because, I need to inform recipients 1,2 in case of failure and recipients 1,2,3,4,5,6 in case of success. I rolled back email-ext to 2.20 temporary as a quick solution.

          Alex Earl added a comment -

          Can you get a thread dump of what is going on when its in this state?

          Alex Earl added a comment - Can you get a thread dump of what is going on when its in this state?

          Alex Earl added a comment -

          As an update if other people are running into this issue, it looks like it is related to having a version of token-macro installed that is less than 1.5.1.

          Alex Earl added a comment - As an update if other people are running into this issue, it looks like it is related to having a version of token-macro installed that is less than 1.5.1.

          Alex Earl added a comment -

          Added catch of NoSuchMethodError when calling token-macro in case token-macro is too old.

          Alex Earl added a comment - Added catch of NoSuchMethodError when calling token-macro in case token-macro is too old.

          Code changed in jenkins
          User: slide
          Path:
          src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java
          src/main/java/hudson/plugins/emailext/plugins/ContentBuilder.java
          http://jenkins-ci.org/commit/email-ext-plugin/f4eff284765512889f34666c0d71887cbab0971e
          Log:
          Fix JENKINS-14224

          • Added a catch for NoSuchMethodError which could occur if token-macro is too old.

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: slide Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/java/hudson/plugins/emailext/plugins/ContentBuilder.java http://jenkins-ci.org/commit/email-ext-plugin/f4eff284765512889f34666c0d71887cbab0971e Log: Fix JENKINS-14224 Added a catch for NoSuchMethodError which could occur if token-macro is too old.

          Thank you for the solution.

          Alexey Gavrilov added a comment - Thank you for the solution.

            slide_o_mix Alex Earl
            alg Alexey Gavrilov
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: