I'm having trouble understanding if this is even possible from the documentation
I want to configure travis so that the author and committer are notified of any build failures. But I also want to notify a specific email address at all times, regardless if they are the author or not.
From what I understand, adding the following to .travis.yml removes the emailing the committer and author:
notifications:
email:
recipients:
- someone#example.com
on_success: change
on_failure: always
Is what I'm looking for possible, and If so what do I need to specify in notifications?
No, it's not possible, see https://docs.travis-ci.com/user/notifications#How-is-the-build-email-receiver-determined%3F:
If there’s a setting specified, Travis CI only sends an emails to the addresses specified there, rather than to the committer and author.
Related
I'm struggling with duplicated users in my Jenkins and Not sending mail to unregistered user ... problem.
I installed the plugin as per this answer but cannot configure it properly by reading the plugin documentation.
My jenkins collects data from Active Directory and some users have duplicated entry, e.g.:
john.doe, john.doe#mycompany.com -> duplicated user which is detected by Jenkins
doej, john.doe#mycompany.com -> correct user which is used when logging in
Jenkins after collecting responsible people from git changes in job ends with
Not sending mail to unregistered user john.doe#mycompany.com
I tried adding additional identity to user doej by setting:
Identity: john.doe#mycompany.com
Realm: <empty>
but it doesn't work.
How should I configure correctly the Additional Identities Plugin?
Seems it's not possible to configure the additional identity plugin in Jenkins for merge the duplicate user
As Jenkins is missing a way to ensure users unicity(unique) since they are created from various sources: authentication method (LDAP in my case), code commits (Subversion, Mercurial, Git, ...).
Depending on the way the user is retrieved by Jenkins (from a commit on a given SCM or its authentication), multiple identities are created for the same real user.
As a consequence, some features are not fully or badly working (login, notifications, user's builds, continuous integration game, ...) and configuration of users is a pain as it must be done multiple times for each real user.
Still the required features are:
a merging features. Allow to merge multiple Jenkins users into a single account.
a user pattern per SCM. Allow to choose how to extract a username from a commit for each SCM and how to optionally match existing one instead of creating a new user.
an id pattern per notification type. Allow to define how to generate the default id used for notification from the user data (from his jenkins id, his name, his scm id, ...): for instance, his mail or his jabber id, ...
Reference: [JENKINS-10258] Allow users unicity - Jenkins Jira
Solution is Jenkins 1.480 but this is still in Vulnerabilities state and have bug as well.
Jenkins 1.480 introduces an extension point to resolve jenkins user "canonical" ID when searching for user in Database by id or full name. This plugin uses this extension point to let user configure external identities as user properties.
You can reach out to Jenkins community or Support team to know the status or when they will final release
According to these instructions:
If there’s a setting specified, Travis CI only sends an emails to the addresses specified there, rather than to the committer and author.
Is there a way to get an email sent both to the committer/author and an additional email list?
I contacted Travis support and it sounds like this is not currently possible:
from: Dominic Jodoin support#travis-ci.com
date: Sep 14, 2018, 7:47 AM
Thanks for reaching out and I'm sorry for the delay of my reply.
What you describe is unfortunately not possible at this time. The notifications settings in your .travis.yml file will always have precedence. Sorry for the inconvenience.
I've added your feature request to our backlog and added a note to contact if/when this gets prioritized and implemented.
Don't hesitate to reach out again in the future for any other questions or problems you might have with Travis CI. We would be happy to help you further.
Cheers,
-- Dominic.
In the Gerrit documentation there is no configuration setting, which could be used to automatically send emails if there was no action with a commit for a given period of time.
There is a notification type, abandoned_changes, but it means that the change was already abandoned.
What I want is an e-mail notification if the commit was not abandoned, but there was no action with it, like Hey, do you really need this commit?
You can't configure Gerrit to send this type of notification but you can search for open changes which are not updated for a while like in the following example:
is:open AND age:1week
See more info about search operators here.
You can make a script (bash, perl, etc) to execute the query using REST and send the result by e-mail.
See more info about query changes using REST here.
Is there a way you can send an email to a distribution list? This is not working as only the individual email addresses are working fine. Is there any setting that i am missing?
I dealt with this issue and found out it had to do with mail server restrictions put in place by Sys Admins at my workplace.
A lot of places have rules in place regarding which users or servers can access distribution lists, so the first thing I would do is ask your SA team if such restrictions exist.
Another thing to try (as another answer stated) is setting default content type to text/html - assuming above restrictions aren’t the cause.
I was having the same issue with this plugin. I could send emails to individual users but not to groups/DLs.
Try to set the default content type to HTML (text/HTML) and it will start to work.
Is it possible to setup TFS/Test Manager so that it sends out an email after a test fails?
Yes, it is possible but it requires quite a lot of changes/additions to the process template and possibly a custom-made activity.
After tests have run, we check if BuildDetail.BuildPhaseStatus has status failed
We send mail to everyone who has changesets committed to this build, so the build goes through BuildDetail.AssociatedChangesets (you need to have AssociateChangesetsAndWorkItems on) and get the committer username.
Unfortunately for us, there's no good correlation between TFS username and email address at our place, so we had to create a custom activity that looks that up in the AD.
The actual email is sent with the BuildReport action from Community TFS Build Extensions. We modified the xslt, but that's not really necessary. We also wanted to include a listing of the failed tests, and that required modification of the action itself (test data isn't included by default).
Looking at this description and all the work made to get this working, I'm beginning to wonder if it was worth it ;).