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

emailext not sending mails to culprits/develoeprs

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not A Defect
    • Icon: Minor Minor
    • email-ext-plugin
    • None

      I use emailext in a multibranch pipeline with 

      recipientProviders:[culprits()]

      and also with

      recipientProviders: [developers()]

      Both scenarios are failing.
       
      I get 

      Not sending mail to user user.name@company.com with no permission to view 001_sandbox  » multibranch test » master #34An attempt to send an e-mail to empty list of recipients, ignored.

      The correct user ("user.name@company.com") is recognized.  As the log suggests, the user has no permission to view the Jenkins job, but that's not true. This user is able to see (and run) the multibranch pipeline in Jenkins UI.

       

      I use Atlassian Crowd as user management system and enabled project-based security.

      In https://jenkins.mycompany.com/user/username/configure I can see the correct email address ("user.name@company.com") is set for that user.

          [JENKINS-66573] emailext not sending mails to culprits/develoeprs

          Alex Earl added a comment -

          Does the person have Item.READ permissions?

          Alex Earl added a comment - Does the person have Item.READ permissions?

          kunjan added a comment -

          slide_o_mix can't this be done without giving any permissions? munchkin did you found any workaround?

          kunjan added a comment - slide_o_mix can't this be done without giving any permissions? munchkin did you found any workaround?

          Alex Earl added a comment -

          No, for security reasons, you have to have Item.READ permissions to receive emails for a job.

          Alex Earl added a comment - No, for security reasons, you have to have Item.READ permissions to receive emails for a job.

            Unassigned Unassigned
            munchkin Steffen Becker
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: