TechPrufer
Get started
GitLab
GitLab logoGitLab · Feature trail

Pipeline Failure Notifications

1 post · Jun 2020 – Sep 2025

What this trail covers

GitLab now sends notifications when a pipeline is fixed, in addition to when it fails. This feature aims to reduce the need for developers to constantly monitor pipeline statuses, allowing them to focus on other tasks. Users can customize these notifications at the project or global level. This post introduces Distributed Tracing for enhanced observability and real-time updates for CI job statuses, significantly reducing API calls and improving user experience. The implementation of GraphQL subscriptions with WebSockets has drastically reduced API calls for CI job status updates, moving from polling to an event-driven model for instant feedback and reduced database load.

All GitLab trails
  1. How we supercharged GitLab CI statuses with WebSocketsThis post details the technical implementation of replacing polling for CI job status updates with GraphQL subscriptions over WebSockets using ActionCable. It quantifies the reduction in API calls (92.56%) and network traffic, and discusses the benefits of an event-driven architecture over polling for real-time data. The next steps involve extending this to other parts of the CI/CD workflow.
  2. Top 10 technical articles of 2022This post highlights the troubleshooting of pipeline failures, specifically mentioning the importance of asking questions about code, tests, and vulnerabilities. It also references a blog post on debugging pipeline failures and a post on Git Rebase. The post also discusses reducing 502 errors by caring about PID 1 in containers and breaking down CI/CD complexity with parent-child and multi-project pipelines. It also touches on bug bounties and coding on an iPad with GitPod, and bringing DevOps to the database with Liquibase. Finally, it covers IaC security and GitOps with GitLab.
  3. Notification emails when pipelines are fixedThis post introduces the capability to send notification emails when a pipeline is fixed, complementing the existing failure notifications. It details how to configure these notifications at both the project and global levels, and provides instructions for disabling the feature. The rollout is gradual, with the intention to enable it by default if tests are successful.