Event Types
The relay consumes the CloudEvents emitted by Tekton Pipelines. This page lists what is accepted and how each type maps to the relay’s event.State.
Supported CloudEvent types
CloudEvent type (Ce-Type) | Resource | Relay state |
|---|---|---|
dev.tekton.event.pipelinerun.started.v1 | pipelinerun | running |
dev.tekton.event.pipelinerun.running.v1 | pipelinerun | running |
dev.tekton.event.pipelinerun.successful.v1 | pipelinerun | success |
dev.tekton.event.pipelinerun.failed.v1 | pipelinerun | failure |
dev.tekton.event.pipelinerun.unknown.v1 | pipelinerun | error |
dev.tekton.event.taskrun.started.v1 | taskrun | running |
dev.tekton.event.taskrun.running.v1 | taskrun | running |
dev.tekton.event.taskrun.successful.v1 | taskrun | success |
dev.tekton.event.taskrun.failed.v1 | taskrun | failure |
dev.tekton.event.taskrun.unknown.v1 | taskrun | error |
dev.tekton.event.customrun.started.v1 | customrun | running |
dev.tekton.event.customrun.running.v1 | customrun | running |
dev.tekton.event.customrun.successful.v1 | customrun | success |
dev.tekton.event.customrun.failed.v1 | customrun | failure |
dev.tekton.event.customrun.unknown.v1 | customrun | error |
dev.tekton.event.triggers.started.v1 | eventlistener | running |
dev.tekton.event.triggers.running.v1 | eventlistener | running |
dev.tekton.event.triggers.successful.v1 | eventlistener | success |
dev.tekton.event.triggers.failed.v1 | eventlistener | failure |
dev.tekton.event.triggers.unknown.v1 | eventlistener | error |
States are lowercase — keep that in mind when writing CEL expressions (event.State == "failure", never "Failure").
Unknown types
Events with an unregistered type are dropped early with a no decoder registered for event type log line and counted in events_unsupported_type_total. This usually happens after a Tekton upgrade introduces a new event type — open an issue with the logged type.
Filtering by resource
You can disable whole resource types under filter: in the config (e.g. allow_taskrun: false to ignore TaskRun events entirely) — cheaper than filtering each action with when. See the Configuration Reference.