Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign up[RFC] Add failed build notifications #485
Closed
+5
−0
Conversation
Configure Travis to send emails whenver there is a failed build. Use an email alias (github-saltfs@servo.org) to ensure all interested parties can receive emails, instead of just the author and committer. Per the docs (https://docs.travis-ci.com/user/notifications/), emails are only sent for branches (e.g. master/nightly/auto). This is meant for notifications on failed nightly builds, so always notify on failures but avoid notifying on success.
|
Helps with #376, see discussion there about notification methods. |
|
Superseded by #598. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
aneeshusa commentedSep 23, 2016
•
edited by larsbergstrom
Configure Travis to send emails whenver there is a failed build.
Use an email alias (github-saltfs@servo.org) to ensure all interested
parties can receive emails, instead of just the author and committer.
Per the docs (https://docs.travis-ci.com/user/notifications/), emails
are only sent for branches (e.g. master/nightly/auto).
This is meant for notifications on failed nightly builds, so always
notify on failures but avoid notifying on success.
This change is