Keptn v1 reached EOL December 22, 2023. For more information see https://bit.ly/keptn
Home / Keptn v1 Docs / Release 1.y.z / Define Keptn Projects / Tasks and sequences
Tasks and sequences
In Start a project,
you defined a shipyard.yaml file
and used that to create your project.
You can create a project with a shipyard that only has stages
but it does not do anything until you populate sequences and tasks in those stages.
- A
sequenceis an ordered list of tasks that are triggered sequentially. By default, a sequence is a standalone section that runs and finishes, although you can define a certain sequence to run only after another sequence completes, or you can specify that it runs only if another sequence runs successfully or if the other sequence fails; this essentially forms a chain of sequences. - A single
taskis the smallest executable unit. Remember that, in Keptn, ataskdefines what to do (run a performance test or try to repair a problem on your site) but does not define how to do that (such as which tool to use).
Sequences can be triggered in a variety of ways; see Triggers for details and examples or watch the Trigger a Keptn Sequence video for a demonstration of triggering a sequence using the Keptn Bridge.
The Lifecycle of a Keptn task video discusses how Keptn executes tasks by issuing events.
For more details about tasks and sequences, see the shipyard reference file
Other pages in this section show specific examples of how to define sequences and tasks for various purposes.
