Tekton Step: Difference between revisions
(Created page with "=Internal= * Tekton Concepts =Overview= A '''step''' is an operation in a CI/CD workflow. An example is Java compilation or execution of unit tests....") |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
=Overview= | =Overview= | ||
A '''step''' is an operation in a CI/CD workflow. An example is Java compilation or execution of unit tests. Each step is performed within a container image provided when the step is defined. A step processes a set of [[#Input|inputs]] and produces a set of [[#Output|outputs]]. Steps do not exist in isolation, they are part of [[#Task|tasks]], and they are executed as running containers with the task's pod. As such, a task's steps may share a volume, that allows them to exchange data. These containers are referred to as <span id='Step_Container'></span>'''step containers'''. | A '''step''' is an operation in a CI/CD workflow. An example is Java compilation or execution of unit tests. Each step is performed within a container image provided when the step is defined. A step processes a set of [[Tekton_Concepts#Input|inputs]] and produces a set of [[Tekton_Concepts#Output|outputs]]. Steps do not exist in isolation, they are part of [[Tekton_Concepts#Task|tasks]], and they are executed as running containers with the task's pod. As such, a task's steps may share a volume, that allows them to exchange data. These containers are referred to as <span id='Step_Container'></span>'''step containers'''. | ||
=Task Step Definition= | =Task Step Definition= | ||
{{External|https://tekton.dev/docs/pipelines/tasks/#defining-steps}} | {{External|https://tekton.dev/docs/pipelines/tasks/#defining-steps}} | ||
A [[#Task_Manifest|task manifest]] contains an array of step declarations. Each step has an optional name, and defines a container image that execute the step functionality on a specific input and produces a specific output. The order in which the step declarations appear in the array is the order in which the steps will execute. | A [[Tekton_Concepts#Task_Manifest|task manifest]] contains an array of step declarations. Each step has an optional name, and defines a container image that execute the step functionality on a specific input and produces a specific output. The order in which the step declarations appear in the array is the order in which the steps will execute. | ||
<font color=darkkhaki>TO PROCESS.</font> | <font color=darkkhaki>TO PROCESS.</font> | ||
=Container Contract= | |||
<font color=darkkhaki>TO PROCESS: https://tekton.dev/docs/pipelines/container-contract/</font> | |||
Latest revision as of 04:27, 29 April 2022
Internal
Overview
A step is an operation in a CI/CD workflow. An example is Java compilation or execution of unit tests. Each step is performed within a container image provided when the step is defined. A step processes a set of inputs and produces a set of outputs. Steps do not exist in isolation, they are part of tasks, and they are executed as running containers with the task's pod. As such, a task's steps may share a volume, that allows them to exchange data. These containers are referred to as step containers.
Task Step Definition
A task manifest contains an array of step declarations. Each step has an optional name, and defines a container image that execute the step functionality on a specific input and produces a specific output. The order in which the step declarations appear in the array is the order in which the steps will execute.
TO PROCESS.
Container Contract
TO PROCESS: https://tekton.dev/docs/pipelines/container-contract/