I have configured an editable email plugin and it works well. However, in some cases (which I really don't know) the emails are not being triggered.
I configured it to send email in both Success and Failure - Any case
The console output is as follows
Checking for post-build
Performing post-build step
Checking if email needs to be generated
No emails were triggered.
Finished: UNSTABLE
I have configured Failure - any as shown below. It looks like for a specific condition jenkins decides not to trigger email!
Related
I am using email-ext plugin to trigger emails after the build fails or become unstable. The build becomes unstable when some of the tests fail and the build fails when the compilation fail.
Can we use conditions to display different customized subject depending on the cause of the email trigger?
Yes, below the Editable email notification interface there should be an Advanced settings.. button which will give you access to various triggers. As you add & configure the triggers, you'll note an Advanced.. button for each of them, which will allow you to fully customize the e-mail template.
I am using the email-ext plugin v.2.38.1 (post-build action "Editable Email Notification") on Jenkins v.1.566 to send e-mails after the build when certain conditions are met.
When using multiple post-build actions, I got the impression that the email-ext plugin always comes last and is executed after all other actions, no matter how I put the order of actions in the configuration. Other plugins respect the order and are executed accordingly as described in this issue.
Is there any possibility to execute another post-build action after sending the e-mails? In my case, I would like to run a shell script doing some clean-up in the workspace which cannot run before because it will delete a file that is part of the e-mail body.
One could work around this by defining an extra clean-up job which is triggered after the main job is completed, however, I would prefer having everything defined in one job only.
The emailing is a publishing action which occures always after build and post build actions ..
Additionally I think you should clean something before running the job (at startup eventually) but never at the end.
How can you study your issues if you destroy all materials that should enable you to do so ?
The step Editable Email Notification is always executed at last in the post-build actions, but you can use a Editable Email Notification Templates step which can be executed in the order you specified in post-build actions
I have a Matrix job (Job A) with that call build sub job (B) using Jenkins Parameterized Trigger plugin.
In the Parent Job (Mtrix) i use Editable Email Notification to trigger each configuration.
I want to get 15 lines from child job (B) build log for each configuration to add it in the email (if the build fails).
How can I do such thing ?
This plugin allows you to configure every aspect of email notifications. You can customize when an email is sent, who should receive it, and what the email says.
here is the link : https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin
Steps to reproduce my problem:
Using GIT for SCM and Jenkins is set up to trigger build on SCM change
Master branch is building fine and all tests are passing
Create new branch from master
Break something so build fails and push to the new branch
Build is triggered in Jenkins by SCM change
Expected result is that email-ext plugin sends notification of build failure to the person who first pushed to the new branch.
But actually no e-mail is sent and the log says:
Email was triggered for: Failure - Any
Sending email for trigger: Failure - Any
An attempt to send an e-mail to empty list of recipients, ignored.
Finished: FAILURE
The "Failure - Any" trigger has both Developers and Culprits set under "Send To".
When a second commit is made to the new branch by the same person, the trigger works fine - it finds the e-mail address of the culprit and sends the e-mail.
Using Email-ext version 2.38.1, Jenkins 1.575.
The triggers I have configured:
Screenshot from the first failing build after creating a new branch is below. (Branch is immediately broken)
I think the problem might be that it says "No changes", although it is triggered by a SCM change.
If it is changed with a second commit, it will show that commit under "Changes" and then it knows who to send the e-mail to.
Any way to get the plugin to send an e-mail to the one who creates the broken branch? Thank you.
I'm trying to send e-mail to culprits when the build fails. If I start the build manually the e-mail is sent, but If I start the build through SCM polling e-mail is not send and the console output for the build shows the message:
An attempt to send an e-mail to empty list of recipients, ignored.
Is that the right way the plugin should work (culprit should be a person, not scm polling)?
Im using:
OS: Ubuntu Server 11.04
Jekins: 1.532.1
Email-ext plugin: 2.37.2
Currently (before the next release 2.38) when you want to send emails to the culprits you also need to check the "Developers" checkbox. Without it, the culprits portion will not be used at all.
This will be different going forward, adding Culprits as a recipient list will do what is expected.