Implement trigger: Pipeline Failed (pipeline_failed)

Summary

Developers spend days sifting through 15K-line logs when pipelines fail in the Verify stage. This trigger automates failure diagnosis and triage the moment a pipeline fails.

Audit Event Name: pipeline_failed


Agent Examples

Agent 1 — Auto-Diagnose & Fix Pipeline Agent

Automatically reads the pipeline failure, diagnoses the root cause, checks the CI configuration, and proposes a fix via a new branch and merge request with a plain-English diagnosis comment.

Tools:

  • Get Pipeline Errors
  • Get Pipeline Failing Jobs
  • Get Repository File
  • Create Commit
  • Create Merge Request
  • Create Merge Request Note

Agent 2 — Pipeline Failure Triage & Notify Agent

Reads the failure details, searches recent commits to identify the likely breaking change, and creates an issue linking the failure to the responsible commit and assignee.

Tools:

  • Get Pipeline Errors
  • List Commits
  • Get Commit Diff
  • Create Issue
  • Create Issue Note

Implementation Notes & Caveats

⚠️ pipeline_failed is not yet in the audit event enum. This event needs to be added before the trigger can ship. Cross-reference with the EventStore integration in gitlab-com/content-sites/handbook!18106 before implementation.

Edited by 🤖 GitLab Bot 🤖