Tekton Events Relay
Tekton emits CloudEvents. Your platforms get updated. Automatically.
Tekton Events Relay is a production-ready CloudEvents bridge that turns Tekton PipelineRun/TaskRun events into commit statuses, PR comments, labels, deployments and chat notifications β across 6 SCM platforms and 8 notification channels, with CEL-based routing and Go-template customization.
flowchart LR
TK[Tekton Pipelines] -- CloudEvents --> R{{Tekton Events Relay}}
R -- statuses Β· comments Β· labels Β· deployments --> SCM[GitHub Β· GitLab Β· Gitea<br/>Bitbucket Β· Azure DevOps Β· SourceHut]
R -- notifications --> CHAT[Slack Β· Teams Β· Discord]
R -- alerts & markers --> OPS[PagerDuty Β· Datadog<br/>Grafana Β· Sentry]
R -- JSON payloads --> HOOK[Generic Webhooks]
Why use it?
Without the relay, reporting CI status means adding notification Tasks and finally blocks to every pipeline, duplicating credentials and API logic everywhere. With the relay, pipelines stay clean: one deployment, one config, and routing decisions live in CEL expressions β not in pipeline YAML.
The only integration contract is a set of annotations on your PipelineRuns (set once in your TriggerTemplate). No extra Tasks, steps, sidecars or results required.
Start here
| I want to⦠| Go to |
|---|---|
| Get it running in 10 minutes | Quickstart |
| Install and tune the Helm chart | Installation |
| Understand the annotation contract | Annotations |
| See every config option | Configuration Reference |
| Pick actions per provider | Actions |
| Filter and route events | CEL Expressions |
| Customize messages | Templates |
| Run it in production | Operations Β· Observability |
| Understand the internals | Architecture |
| Fix something | Troubleshooting |
Capability matrix
| Action | GitHub | GitLab | Gitea | Bitbucket | Azure DevOps | SourceHut |
|---|---|---|---|---|---|---|
commit_status | β | β | β | β | β | β |
commit_comment | β | β | β | β | β | β |
pr_comment (+ upsert) | β | β | β | β * | β | β |
issue_comment | β | β | β | β | β | β |
discussion_comment | β | β β | β | β | β | β |
check_run | β | β | β | β | β | β |
deployment_status | β | β | β | β | β | β |
label (add/remove) | β | β | β | β | β | β |
* Bitbucket Cloud supports mode: upsert; Bitbucket Server falls back to create. β GitLab discussion_comment posts a resolvable MR discussion thread (MR-only).
Production-ready by default
- Reliability β exponential-backoff retries with jitter and
Retry-Afterawareness, per-handler timeouts, HTTP 503 back-pressure, dead letter queue with replay. - Correctness β event deduplication, idempotent comments (
mode: upsert), pluggable state backends (memory / Valkey / Olric) for multi-replica deployments. - Operations β hot configuration reload, rich
/readyz, Prometheus metrics, OpenTelemetry tracing. - Security β HMAC webhook validation with replay protection, native TLS, custom CA support, Cosign-signed releases.