-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
master node on Ubuntu x64
slave node on Windows
I send my mail via groovy script in a multibranch-pipeline (blue ocean)
script { def currResult = getResultAsString(currentBuild) def prevResult = getResultAsString(currentBuild.getPreviousBuild()) if (currResult != "SUCCESS" || prevResult != "SUCCESS") { echo 'send mail' emailext body: '''${SCRIPT, template="my-html.template"}''', recipientProviders: [[$class: 'DevelopersRecipientProvider'], [$class: 'CulpritsRecipientProvider'], [$class: 'UpstreamComitterRecipientProvider'], ], subject: '[Jenkins]: ${JOB_NAME} ${BUILD_DISPLAY_NAME} - ' + currResult, mimeType: 'text/html' } } def getResultAsString(build) { def result = build?.result if (result == null) { result = "SUCCESS" } return result; }
When creating a new branch and adding a commit which will fail this build,
jenkins will not send a email, with following message:
An attempt to send an e-mail to empty list of recipients, ignored.
However, when adding another commit to the same branch, jenkins, will now surprisingly have a commiter email address and can send the email.
So always the first build of a new branch, email-ext will not retrieve a correct email from the commit.
Can you please fix it?
[JENKINS-51218] EMail-Ext does not send email, because or empty recipients
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Attachment | New: jenkins_changes.jpg [ 42564 ] |
Component/s | New: git-plugin [ 15543 ] | |
Component/s | New: scm-api-plugin [ 18054 ] |
Component/s | Original: email-ext-plugin [ 15538 ] |
Assignee | Original: David van Laatum [ davidvanlaatum ] | New: Mark Waite [ markewaite ] |
Resolution | Original: Won't Fix [ 2 ] | |
Status | Original: Closed [ 6 ] | New: Reopened [ 4 ] |
This is not actually a fault with emailext its with the SCM api. First build has no build to compare it to so no way to determine what has happened since. emailext purely asks the SCM api for this info