Continuous Delivery Core Events

December 22, 2025 · View on GitHub

Continuous Delivery Core Events include the subjects and predicates related to orchestration of execution required to deterministically and continuously delivery software to users. Core events are at the lower level of abstraction in the dictionary: they describe the status of an execution, but they don't include any semantic about the function of the execution itself. These events are generated by pipeline orchestration engines.

Subjects

In the context of Continuous Delivery, a pipeline is the definition of a set of tasks that needs to be performed to build, test, package, release and deploy software artifacts. The definition of pipelines and tasks is an authoring process, and has no event associated to it. CDEvents identifies two subjects, pipelineRun and taskRun, which are the runtime counterparts of pipelines and tasks.

SubjectDescriptionPredicates
pipelineRunAn instance of a pipelinequeued, started, finished
taskRunAn instance of a taskstarted, finished

pipelineRun

A pipeline can be instantiated multiple times, for example to build different versions of the same artifact. We are referring to this instance as pipelineRun. It will have a unique id and it will help us to track the build and release progress on a particular software artifact.

FieldTypeDescriptionExamples
idStringSee idtenant1/12345-abcde, namespace/pipelinerun-1234
sourceURI-ReferenceSee source
pipelineNameStringThe name of the pipelineMyPipeline, Unit tests for my repo
outcomeStringoutcome of a finished pipelineRunsuccess, failure, cancel, or error
urlURIurl to the pipelineRunhttps://dashboard.org/namespace/pipelinerun-1234, https://api.cdsystem.com/namespace/pipelinerun-1234
errorsStringIn case of error, canceled, or failed pipeline , provides details about the failureInvalid input param 123, Timeout during execution, pipelineRun canceled by user, Unit tests failed

taskRun

Pipelines are composed by as a set of Tasks to be performed, like performing a build, running some tests, publishing an artifact. A taskRun is an instance of a Task, typically part of a pipeline. If a Pipeline is composed by a single Task, the execution of pipelineRun MUST generate both the pipelineRun and taskRun events. Some systems may support execution of Tasks without a Pipeline associated, in which case it is acceptable to generate only taskRun events.

FieldTypeDescriptionExamples
idStringSee idtenant1/12345-abcde, namespace/taskrun-1234
sourceURI-ReferenceSee source
taskNameStringThe name of the pipelineMyPipeline, Unit tests for my repo
pipelineRunObject (pipelineRun)The pipelineRun that this taskRun belongs to.{"id": "namespace/pipelinerun-1234"}
outcomeStringoutcome of a finished taskRunsuccess, failure, cancel, or error
urlURIurl to the taskRunhttps://dashboard.org/namespace/taskrun-1234, https://api.cdsystem.com/namespace/taskrun-1234
errorsStringIn case of error, canceled, or failed pipeline , provides details about the failureInvalid input param 123, Timeout during execution, taskRun canceled by user, Unit tests failed

Events

pipelineRun queued

Due the dynamic nature of Pipelines, most of actual work needs to be queued to happen in a distributed way, hence queued events are added. Adopters can choose to ignore these events if they don't apply to their use cases.

  • Event Type: dev.cdevents.pipelinerun.queued.0.3.0
  • Predicate: queued
  • Subject: pipelineRun
FieldTypeDescriptionExamplesRequired
idStringSee idtenant1/12345-abcde, namespace/pipelinerun-1234
sourceURI-ReferenceSee source
pipelineNameStringThe name of the pipelineMyPipeline, Unit tests for my repo
urlURIurl to the pipelineRunhttps://dashboard.org/namespace/pipelinerun-1234, https://api.cdsystem.com/namespace/pipelinerun-1234

pipelineRun Started

A pipelineRun has started and it is running.

  • Event Type: dev.cdevents.pipelinerun.started.0.3.0
  • Predicate: started
  • Subject: pipelineRun
FieldTypeDescriptionExamplesRequired
idStringSee idtenant1/12345-abcde, namespace/pipelinerun-1234
sourceURI-ReferenceSee source
pipelineNameStringThe name of the pipelineMyPipeline, Unit tests for my repo
urlURIurl to the pipelineRunhttps://dashboard.org/namespace/pipelinerun-1234, https://api.cdsystem.com/namespace/pipelinerun-1234

pipelineRun Finished

A pipelineRun has finished, successfully or not.

  • Event Type: dev.cdevents.pipelinerun.finished.0.3.0
  • Predicate: finished
  • Subject: pipelineRun
FieldTypeDescriptionExamplesRequired
idStringSee idtenant1/12345-abcde, namespace/pipelinerun-1234
sourceURI-ReferenceSee source
pipelineNameStringThe name of the pipelineMyPipeline, Unit tests for my repo
urlURIurl to the pipelineRunhttps://dashboard.org/namespace/pipelinerun-1234, https://api.cdsystem.com/namespace/pipelinerun-1234
outcomeString (enum)outcome of a finished pipelineRunsuccess, failure, cancel, or errorsuccess, failure, cancel, error
errorsStringIn case of error, canceled, or failed pipeline , provides details about the failureInvalid input param 123, Timeout during execution, pipelineRun canceled by user, Unit tests failed

taskRun Started

A taskRun has started and it is running.

  • Event Type: dev.cdevents.taskrun.started.0.3.0
  • Predicate: started
  • Subject: taskRun
FieldTypeDescriptionExamplesRequired
idStringSee idtenant1/12345-abcde, namespace/taskrun-1234
sourceURI-Referencesource from the context
taskNameStringThe name of the pipelineMyPipeline, Unit tests for my repo
pipelineRunObject (pipelineRun)The pipelineRun that this taskRun belongs to.{"id": "namespace/pipelinerun-1234"}
urlURIurl to the taskRunhttps://dashboard.org/namespace/taskrun-1234, https://api.cdsystem.com/namespace/taskrun-1234

taskRun Finished

A taskRun has finished, successfully or not.

  • Event Type: dev.cdevents.taskrun.finished.0.3.0
  • Predicate: finished
  • Subject: taskRun
FieldTypeDescriptionExamplesRequired
idStringSee idtenant1/12345-abcde, namespace/taskrun-1234
sourceURI-Referencesource from the context
taskNameStringThe name of the pipelineMyPipeline, Unit tests for my repo
pipelineRunObject (pipelineRun)The pipelineRun that this taskRun belongs to.{"id": "namespace/pipelinerun-1234"}
urlURIurl to the taskRunhttps://dashboard.org/namespace/taskrun-1234, https://api.cdsystem.com/namespace/taskrun-1234
outcomeString (enum)outcome of a finished taskRunsuccess, failure, cancel, or errorsuccess, failure, cancel, error
errorsStringIn case of error, canceled, or failed pipeline , provides details about the failureInvalid input param 123, Timeout during execution, taskRun canceled by user, Unit tests failed