-
Notifications
You must be signed in to change notification settings - Fork 33
Closed
Labels
RefinedA ticket that's been parsed by the forum of people in backlog refinementA ticket that's been parsed by the forum of people in backlog refinementplannedWork scheduled for an upcoming sprint.Work scheduled for an upcoming sprint.urgency discussedThe urgency of this item has been discussed (probably in Backlog Refinement]The urgency of this item has been discussed (probably in Backlog Refinement]
Description
User Need
As a engineer in an application team
I want to know (in my team's Slack channel) when the deployment of one of my applications fails
so that I can address any issues
Context
This was requested by a user here.
Currently deployment failures are reported in the generic #govuk-deploy-alerts channel. Workflow is here.
Each repo has its owner team (and optionally alerts_team) listed in https://github.com/alphagov/govuk-developer-docs/blob/main/data/repos.yml (also available as JSON).
For Seal alerts, alerts_team is used, with fallback to using team.
See also #1845, which is specifically about E2E test failures.
There's an existing action to report Github workflow run failure to Slack - that will need consideration to avoid duplication/noise.
What’s Needed
- Send alerts for deployment failures to the relevant team Slack channel, based on repos.yml
Acceptance Criteria
- Alerts for deployment failures are sent to the relevant team Slack channel, based on repos.yml
- Relevant documentation is updated
- Announce on #govuk-developers
User Comms Plan (if applicable)
- Announce on #govuk-developers
- Consider a slot at the tech fortnightly meeting
- Reply to this specific conversation
Assumptions (optional)
- [Assumption] The developer wants the alerts_team channel to receive all CD alerts. [Mitigation] Speak to the team. Use the Slack channel if required.
- [Assumption] That we also continue to receive alerts in the #govuk-deploy-alerts channel.
Risks & Mitigation (optional)
- [Risk] Noise; this becomes too noisy for developers. [Mitigation] Control through a bool value or switch/flag that enables this.
- [Risk] We are increasing complexity in our CD system. [Mitigation] Swallow the complexity and accept that we will refactor our CICD in the future.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
RefinedA ticket that's been parsed by the forum of people in backlog refinementA ticket that's been parsed by the forum of people in backlog refinementplannedWork scheduled for an upcoming sprint.Work scheduled for an upcoming sprint.urgency discussedThe urgency of this item has been discussed (probably in Backlog Refinement]The urgency of this item has been discussed (probably in Backlog Refinement]