Module 8 Lesson 1: Pipeline Notifications

You shouldn't have to "Refresh" the GitLab website to know if your build finished. A healthy DevOps culture relies on Immediate Feedback.

1. Built-in Email Notifications

Every GitLab user receives an email by default when:

• A pipeline fails on a branch they pushed to.
• A pipeline succeeds after being "Fixed" (recovered from failure).

Customization: You can go to your Profile -> Notifications to choose:

• "Global": Get emails for everything.
• "Watch": Only for projects you care about.
• "On-close": Only when a failure happens.

---

2. Desktop Notifications

If you use a browser like Chrome or Firefox, GitLab can show a "Desktop Toast" notification. This is the fastest way to know if your tests failed while you are busy writing more code.

---

Visualizing the Process

graph TD
    Start[Input] --> Process[Processing]
    Process --> Decision{Check}
    Decision -->|Success| End[Complete]
    Decision -->|Retry| Process

---

3. Webhooks (The Automation Link)

If you want to do something custom (like light up a "Red" LED bulb in your office when a build fails), you use Webhooks.

1. Go to Settings -> Webhooks.
2. Select the "Pipeline events" trigger.
3. Provide a URL to your own server or an automation platform like n8n (Course ID 11).

---

4. The "Notification Fatigue" Warning

If your pipeline fails 100 times a day, your team will start to "Ignore" the emails.

• The Solution: Only send notifications for "Critical" branches (like main) to the whole team. For experimental branches, only notify the developer who pushed the code.

---

Exercise: The Alert Test

1. Go to your User Settings -> Notifications.
2. Create a "Global" rule that sends an email for every pipeline status change.
3. Push a commit that intentionally fails. Do you get an email?
4. Push a fix. Do you get a "Success" email?
5. Why is "Email" often the worst way to notify a fast-moving engineering team? (Hint: Think about Slack).

---

Summary

Notifications are the "Nerve System" of your pipeline. By ensuring the right people get the right information at the right time, you reduce the "Time to Repair" (Module 1's DORA metrics) and keep your team moving at full speed.

Next Lesson: Real-time chat: Integrating with Slack and Teams.