Hi,
Oh, email-ext, one of my current favorite topics....
I am calling it a little differently and that's working (for me it's jelly instead of groovy but groovy worked before also):
def mailbody = '${JELLY_SCRIPT, template="template.jelly"}'
def mailsubject = 'Jenkins Build ' + currentBuild.fullDisplayName + ' finished: ' + currentBuild.currentResult
emailext attachLog: false, body: mailbody, recipientProviders: [culprits(), brokenTestsSuspects(), brokenBuildSuspects(), upstreamDevelopers()], subject: mailsubject
Anyone familiar with that problem:
"JellyException: Could not parse Jelly script : null"?
I found several solutions to support developing the jelly script:
- the email-ext template-testing link in the job page: not working with scripted pipeline
- a couple lines of groovy script for the script console to trigger new email execution from a finished job: not working due to syntax problems and obviously made for a lot older API
- a lot of published jelly-script snippets to add output from the one and other plugin: a lot of syntax errors everywhere
What's the latest best way to develop this stuff?
Is there any way to trigger exeuction based on an existing job?
Any way to get that origniating parser exception to find the real issue?
BR,
Christoph