Skip to content

Latest commit

 

History

History
41 lines (33 loc) · 1.69 KB

events.md

File metadata and controls

41 lines (33 loc) · 1.69 KB

Events

Tekton runtime resources, specifically TaskRuns and PipelineRuns, emit events when they are executed, so that users can monitor their lifecycle and react to it. Tekton emits kubernetes events, that can be retrieve from the resource via kubectl describe [resource].

No events are emitted for Conditions today (tektoncd#2461).

TaskRuns

TaskRun events are generated for the following Reasons:

  • Started: this is triggered the first time the TaskRun is picked by the reconciler from its work queue, so it only happens if web-hook validation was successful. Note that this event does not imply that a step started executing, as several conditions must be met first:
    • task and bound resource validation must be successful
    • attached conditions must run successfully
    • the Pod associated to the TaskRun must be successfully scheduled
  • Succeeded: this is triggered once all steps in the TaskRun are executed successfully, including post-steps injected by Tekton.
  • Failed: this is triggered if the TaskRun is completed, but not successfully. Causes of failure may be: one the steps failed, the TaskRun was cancelled or the TaskRun timed out.

PipelineRuns

PipelineRun events are generated for the following Reasons:

  • Succeeded: this is triggered once all Tasks reachable via the DAG are executed successfully.
  • Failed: this is triggered if the PipelineRun is completed, but not successfully. Causes of failure may be: one the Tasks failed or the PipelineRun was cancelled.