Commands icon
If icon
SlackIncomingWebhook icon
Schedule icon

Woodpecker CI Pipeline Consecutive Failure Sentinel

Audits Woodpecker CI build pipelines for recurring test and deployment failures.

Categories
CloudInfrastructure

How it works

This workflow connects to the Woodpecker CI REST API (/api/repos/{owner}/{name}/builds) to audit recent pipeline build execution statuses. In modern continuous integration pipelines, consecutive build failures on primary branches indicate broken merge commits, test environment degradation, or docker registry pull authentication issues. This sentinel queries the build history, tallies consecutive non-success executions (failure, error, killed), and dispatches an incident notification to development teams when failures meet or exceed the alert threshold.

What you get

  • Real-time continuous integration pipeline health monitoring.
  • Early detection of broken master/main branches across git repositories.
  • Automated Slack incident notifications with consecutive failure counts.

Who it's for

  • DevOps and Platform Engineers operating self-hosted Woodpecker CI instances.
  • Software Engineering Leads maintaining continuous delivery quality gates.
  • Release Managers ensuring smooth deployment cadence.

Why orchestrate this with Kestra

  • Centralized DevOps Telemetry: Integrates CI/CD monitoring into standard enterprise dashboards.
  • Automated Workflow Orchestration: Can trigger rollback flows or re-run failed stages automatically.
  • Encrypted Credential Security: Secures Woodpecker personal access tokens inside Kestra secrets.

Prerequisites

  • Woodpecker CI server accessible over HTTPS.
  • Personal access token configured in WOODPECKER_API_TOKEN secret.
  • Slack incoming webhook configured in SLACK_WEBHOOK secret.

Quick start

  1. Import this blueprint into your Kestra instance.
  2. Add WOODPECKER_API_TOKEN and SLACK_WEBHOOK secrets.
  3. Specify woodpecker_server_url, repo_owner, and repo_name.
  4. Enable the schedule trigger to activate automatic CI pipeline surveillance.

How to extend

  • Trigger an automatic pipeline restart via POST /api/repos/{owner}/{name}/builds/{number}.
  • Extract failed pipeline step names from /api/repos/{owner}/{name}/builds/{number}.
  • Route notifications to specific development squad Slack channels based on repository tags.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.