[FOLIO-2958] send master-branch build failure notifications to Slack Created: 13/Jan/21 Updated: 02/Feb/21 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | TBD |
| Reporter: | Zak Burke | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Development Team: | FOLIO DevOps |
| Description |
|
It would be helpful for module-maintainers to be notified via Slack when a master-branch build fails because such failures usually require inspection and intervention by the maintainer. Notifications must be specific in order for the relevant repository owners to notice them. Ideally, a notification would specifically mention the maintainer, or be published to a team-specific channel, in order to avoid being lost in the noise on a generic channel where not all notifications are relevant. One option may be to use a unique keyword or phrase that module-maintainers could configure as a keyword in their own slack preferences. |
| Comments |
| Comment by Zak Burke [ 13/Jan/21 ] |
|
I was originally thinking that using Slack's keyword notifications would be a bad idea since it requires maintainers to sign up for notifications, but if we configure the keywords/phrases by some easy algorithm, $repositoryName.master.build-failure, maybe that's just fine and allows for easy self-service "subscriptions" by anybody who wants to sign up. Dunno. The main thing is, I want to know when the stuff I'm responsible for is broken so I can take appropriate action. |