• Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Major Major
    • email-ext-plugin
    • None
    • Jenkins 2.2 and current version of all plugins.

      In Jenkins 2.2 with Ext-email 2.42, I always see "An attempt to send an e-mail to empty list of recipients, ignored." I have one explicit email address set in global configuration and am using $DEFAULT_RECIPIENTS in my project.

          [JENKINS-34731] Can't send email.

          Chris Nelson added a comment -

          In the Advanced settings, Triggers -> Failure - Any listed "Developers" but not "Recipient List." When I add Recipient List my console output says:

          Checking if email needs to be generated
          Email was triggered for: Failure - Any
          Sending email for trigger: Failure - Any
          messageContentType = text/plain; charset=UTF-8
          Adding recipients from project recipient list
          Adding recipients from trigger recipient list
          Setting In-Reply-To since last build was not successful
          Successfully created MimeMessage
          Sending email to: <me>

          If not including the recipient list is the default, that's not very helpful. I would not have expected to have to open Advanced settings to get basic functionality.

          Chris Nelson added a comment - In the Advanced settings, Triggers -> Failure - Any listed "Developers" but not "Recipient List." When I add Recipient List my console output says: Checking if email needs to be generated Email was triggered for: Failure - Any Sending email for trigger: Failure - Any messageContentType = text/plain; charset=UTF-8 Adding recipients from project recipient list Adding recipients from trigger recipient list Setting In-Reply-To since last build was not successful Successfully created MimeMessage Sending email to: <me> If not including the recipient list is the default, that's not very helpful. I would not have expected to have to open Advanced settings to get basic functionality.

          Chris Nelson added a comment - - edited

          A separate issue, I'm sure, but $BUILD_URL doesn't seem to include a protocol. The only reason I am using this plugin instead of the built-in functionality is so that my notification has a clickable link to the job. I guess I at least gain the ability to put "http://$BUILD_URL" in the body but it's odd that the URL is incomplete.

          Chris Nelson added a comment - - edited A separate issue, I'm sure, but $BUILD_URL doesn't seem to include a protocol. The only reason I am using this plugin instead of the built-in functionality is so that my notification has a clickable link to the job. I guess I at least gain the ability to put "http://$BUILD_URL" in the body but it's odd that the URL is incomplete.

          Alex Earl added a comment -

          Not including the recipient list by default for failures is a historical issue. It was that way for a long time and when I tried enabling recipient list for Failures, people were upset that the behavior changed.

          For BUILD_URL, it takes it from the following: jenkins.getRootUrl() + build.getUrl(), check your URL setting in the Manage Jenkins area under "Jenkins Location Configuration"

          Alex Earl added a comment - Not including the recipient list by default for failures is a historical issue. It was that way for a long time and when I tried enabling recipient list for Failures, people were upset that the behavior changed. For BUILD_URL, it takes it from the following: jenkins.getRootUrl() + build.getUrl(), check your URL setting in the Manage Jenkins area under "Jenkins Location Configuration"

          Chris Nelson added a comment -

          Maybe the distribution needs to not be an Advanced feature.

          Chris Nelson added a comment - Maybe the distribution needs to not be an Advanced feature.

          Alex Earl added a comment -

          Sadly, when I tried that, people didn't like it either. I can't please everyone.

          Alex Earl added a comment - Sadly, when I tried that, people didn't like it either. I can't please everyone.

          Christian Höltje added a comment - - edited

          Can you verify that "Recipient List" is setup in the Failure trigger in the Advanced area in the job itself?

           
          How do you do this with a pure pipeline job?

          e.g. using the github organization folder where you cannot edit individual jobs because they are generated from repos/branches in GitHub.

          Christian Höltje added a comment - - edited Can you verify that "Recipient List" is setup in the Failure trigger in the Advanced area in the job itself?   How do you do this with a pure pipeline job? e.g. using the github organization folder where you cannot edit individual jobs because they are generated from repos/branches in GitHub.

          Alex Earl added a comment -

          You don't, pipeline usage doesn't use failure trigger. You just add the recipients directly in the pipeline call to email-ext.

          Alex Earl added a comment - You don't, pipeline usage doesn't use failure trigger. You just add the recipients directly in the pipeline call to email-ext.

          slide_o_mix

          But I get no recipients (unless I trigger the build, in which case I get myself as a RequestorRecipient) for culprits, developers, etc.

          Christian Höltje added a comment - slide_o_mix But I get no recipients (unless I trigger the build, in which case I get myself as a RequestorRecipient) for culprits, developers, etc.

          Alex Earl added a comment -

          Please don't hijack this issue. If you have questions, use the mailing list.

          Alex Earl added a comment - Please don't hijack this issue. If you have questions, use the mailing list.

          Mahesh Bhosale added a comment - - edited

          I suppose you should use "to:"/"cc:"/"bcc:" extensions in the mailing list before recipient's address.

          Mahesh Bhosale added a comment - - edited I suppose you should use "to:"/"cc:"/"bcc:" extensions in the mailing list before recipient's address.

            slide_o_mix Alex Earl
            chrisnelsonpe Chris Nelson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: