jenkins-email-ext

问题 How can i add to a jenkins pipeline an old-style post-build task which sends email when the build fails? I cannot find "Post-build actions" in the GUI for a pipeline. I know that i can wrap the entire build script try/catch, however this seems ugly when the build script is large and continues to send emails even when the job was aborted manually. I would like to achive the same functionality as with the previouse email-ext based post-build action. try { // Do sth } catch(e) { emailext body: '

问题 How can i add to a jenkins pipeline an old-style post-build task which sends email when the build fails? I cannot find "Post-build actions" in the GUI for a pipeline. I know that i can wrap the entire build script try/catch, however this seems ugly when the build script is large and continues to send emails even when the job was aborted manually. I would like to achive the same functionality as with the previouse email-ext based post-build action. try { // Do sth } catch(e) { emailext body: '

问题 I want to fetch project source code from GitLab, archive it and send it via email. Jenkinsfile: def gitlabRepo = 'http://repository.vrpconsulting.com/roman.skaskevich/koshcheck-copy.git' deleteDir() dir('koshcheck-copy') { stage 'Fetch' def curdir = pwd() echo curdir git url: "${gitlabRepo}", branch: 'master' stage 'Archive' zip archive: true, dir: './src', glob: '', zipFile: 'src.zip' def savedZip = archive 'src.zip' echo savedZip stage 'Notify' emailext ( to: 'roman.skaskevich@gmail.com',

问题 I am writing a simple Jenkins declarative script to run 'make' and send an email with the result (success/failure). I can send a simple email using: post { success { mail to:"myname@me.com", subject:"${currentBuild.fullDisplayName} - Failed!", body: "Success!" } failure { mail to:"myname@me.com", subject:"${currentBuild.fullDisplayName} - Failed!", body: "Failure!" } } The resulting email is rather simplistic. How can I call the email-ext plugin from the script to send an old-style post-build

问题 With Jenkins pipeline you are able to set any environment variable through Global Variable called - env . Jelly template in it's turn gives you ability to access Jenkins API including hudson.model.AbstractBuild and hudson.model.AbstractProject objects. Here are the snippets that I use: Jenkinsfile: node { env.MYVAR = 'My variable' emailext body: ${JELLY_SCRIPT, template="myTemplate"}, subject: 'MySubject', to: 'me' } Jelly template (myTemplate): <?jelly escape-by-default='true'?> <!DOCTYPE