-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ci: notify slack when master goes red #10643
Comments
I think we can use this plugin to have a badge in idpe readme that shows up the status of the master branch https://wiki.jenkins.io/display/JENKINS/Embeddable+Build+Status+Plugin influxdb, telegraf has something similar already. So it should help |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions. |
1 similar comment
This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions. |
Circle 2.0 supports slack notifications but doesn't seem to offer a way to only notify when one branch (i.e. master) goes red or is fixed.
It looks like there are some solutions out there to solve this, that involve running a whole separate heroku app or perhaps involving a specific outgoing webhook.
The specific motivation here was #712 and #682 were independently green, but after #712 was merged, #682 was merged cleanly but resulted in a compile error.
There's a separate discussion ongoing about whether we should require PRs to be rebased on master before merging, but even if that happens, we could still see red builds from flaky tests, and we should still receive notifications for that.
The text was updated successfully, but these errors were encountered: