Alert on CI/CD pipeline events
Release notes
Automatic notification that a CI/CD job in a pipeline has failed alerts a user to a problem as soon as it happens which will reduce time to resolution.
With this release, failed CI/CD jobs will show up as GitLab alerts to help users and incident responders correlate delivery events that may have been the root cause of an incident.
Alerting on CI jobs helps users monitor the progress of a fix without having to manually monitor pipelines. Users can spend their time working on other things like updating stakeholders, conference with their team, without worrying missing problems. The alert will notify them is there is something to look into.
Problem to solve
As a user, I only know if a pipeline has failed if I am actively watching the pipeline or checking my email. I have multiple alerts to triage, but failed pipelines aren't on my list.
Intended users
User experience goal
User can easily set up an alert for their CI/CD jobs or on events which show up in the alerts list.
Proposal
Add ability to alert on CI/CD pipelines events.
- Surface alert in Alert list
- Create to-do for new alerts - Note: As of 15.6, whomever triggered the most recent pipeline will get a todo if the pipeline fails
- Create a webhook for alerts to tie into third party paging applications, so on-call users can be notified
Questions
- What events do people want to be alerted for?
- Pipeline failures
- Specific pipelines (edge case)
- What information should the alerts contain?
- The repository the pipeline ran from
- The pipeline number
- The pipeline and stage that failed
- Where should configuration for internal alerts on CI/CD events live?
- If the alert is pushed to a third party application,
Settings -> Webhook - If the alert is within GitLab, admins should be able to set defaults and project owners can configure per project
- If settings get more complex, we could use a configuration file
- If the alert is pushed to a third party application,
Further details
This work supports the Incident Management direction.
Permissions and Security
Documentation
Availability & Testing
What does success look like, and how can we measure that?
We expect to see an increase in Alerts MAU.
What is the type of buyer?
Platform Perry, because he wants to automate pipelines from inception to production.
Is this a cross-stage feature?
Yes! CI/CD is one of GitLab's biggest revenue generators. Adding alerts to CI/CD events will act as a funnel, driving awareness and adoption of Incident management tools.
Links / references
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.