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

Project Recipient List for Email-ext Templates would be useful

    Details

    • Type: Improvement
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Won't Fix
    • Labels:
      None
    • Environment:
      Jenkins 2.46.3
      email-ext 2.59
      emailext-template 1.0
    • Similar Issues:

      Description

      The Email-ext Template Plugin is very useful for easy configuration of standard Email notifications. For example notifying the requestor or the culprits.

      But one point is missing: Each Projects may have an individual list of users, which should receive build mails. So the "Email-ext Template" configuration in the project should have a way to define variables (e.g.  $DEFAULT_RECIPIENTS), which then could be used in the template.

      Without this enhancement you have to configure Email-ext with the explicit user list in addition to the Email-ext-Template. The results in duplicate mails for those users, who appear in both lists (e.g. because they have committed something). This is not good for acceptance. So instead of using the mail-ext-template, the same configuration will be made on every single project in mail-ext instead.

        Attachments

          Activity

          Hide
          slide_o_mix Alex Earl added a comment -

          I think you can do this now using an environment variable in the job itself. Setup the recipients list to have something like ${ENV, var="RECIPIENT_LIST"}, then set it as a job parameter with the comma separated list of recipients. This works for hard coded lists of recipients.

          Show
          slide_o_mix Alex Earl added a comment - I think you can do this now using an environment variable in the job itself. Setup the recipients list to have something like ${ENV, var="RECIPIENT_LIST"}, then set it as a job parameter with the comma separated list of recipients. This works for hard coded lists of recipients.
          Hide
          slide_o_mix Alex Earl added a comment -

          I just tested this and it works just fine, so I am going to close this as won't fix since there is a way to achieve what you want to do.

          Show
          slide_o_mix Alex Earl added a comment - I just tested this and it works just fine, so I am going to close this as won't fix since there is a way to achieve what you want to do.
          Hide
          slide_o_mix Alex Earl added a comment -

          Workaround is to use a parameter to the job and then an ENV token in the template.

          Show
          slide_o_mix Alex Earl added a comment - Workaround is to use a parameter to the job and then an ENV token in the template.
          Hide
          ghostbee saint scott added a comment -

          Alex Earl I don't think your suggested approach meet our requirement.

           

          I think it require more flexibility for project recipients. We don't want to hardcode the default recipients in the Jenkinsfile.

          This feature is for better administration for target project. Without it, no good approach to achieve that.

           

          I've seen some docs in https://jenkins.io/doc/pipeline/steps/email-ext/ demostrating `ListRecipientProvider` option,
          but it seems lamely fo now?

          Show
          ghostbee saint scott added a comment - Alex Earl I don't think your suggested approach meet our requirement.   I think it require more flexibility for project recipients. We don't want to hardcode the default recipients in the Jenkinsfile. This feature is for better administration for target project. Without it, no good approach to achieve that.   I've seen some docs in https://jenkins.io/doc/pipeline/steps/email-ext/  demostrating `ListRecipientProvider` option, but it seems lamely fo now?

            People

            • Assignee:
              slide_o_mix Alex Earl
              Reporter:
              dth Tom Helpstone
            • Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: