-
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?