-
Notifications
You must be signed in to change notification settings - Fork 0
Home
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]
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.
| 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 |
| 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).
-
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.
Getting started
Reference
SCM providers
Notifiers
Running in production
More