Tekton TaskRun: Difference between revisions
(15 intermediate revisions by the same user not shown) | |||
Line 1: | Line 1: | ||
=External= | =External= | ||
* https://tekton.dev/docs/pipelines/taskruns/ | |||
* https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md | * https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md | ||
=Internal= | =Internal= | ||
* [[Tekton Concepts#TaskRun|Tekton Concepts]] | |||
=Overview= | =Overview= | ||
A '''task run''' (or '''taskRun''') instantiates a specific [[# | A '''task run''' (or '''taskRun''') instantiates a specific [[Tekton_Task#Overview|task]] to execute on a particular set of [[Tekton_Concepts#Input|inputs]] and produce a particular set of [[Tekton_Concepts#Output|outputs]], within specific conditions (for example, build flags). A task run connects [[Tekton_Concepts#Resource|resources]] with [[Tekton_Task#Overview|tasks]]. A task run can be created individually via CLI, by a [[Tekton_PipelineRun#Overview|pipeline run]], as part of a pipeline, or by a Tekton components such as [[Tekton_Concepts#Tekton_Triggers|Tekton Triggers]]. The task run is implemented as a Kubernetes custom resource. | ||
The task run can be used to parameterize the task. Specific values for [[#Task_Parameters|task parameters]] can be declared in the task run. | The task run can be used to parameterize the task. Specific values for [[Tekton_Parameters#Task_Parameters|task parameters]] can be declared in the task run. | ||
= | |||
=Example= | |||
A simple taskrun example: | A simple taskrun example: | ||
<syntaxhighlight lang='yaml'> | <syntaxhighlight lang='yaml'> | ||
Line 19: | Line 23: | ||
</syntaxhighlight> | </syntaxhighlight> | ||
= | =Manifest= | ||
<font size=-1> | <font size=-1> | ||
apiVersion: tekton.dev/v1beta1 <font color=teal># required field</font> | apiVersion: tekton.dev/v1beta1 <font color=teal># required field</font> | ||
Line 26: | Line 30: | ||
name: <font color=indigo><''taskrun-name''></font> <font color=teal> # required field</font> | name: <font color=indigo><''taskrun-name''></font> <font color=teal> # required field</font> | ||
spec: <font color=teal> # required field</font> | spec: <font color=teal> # required field</font> | ||
[[# | [[#Parameters|params]]: | ||
- name: <font color=indigo><''parameter-name''></font> | - name: <font color=indigo><''parameter-name''></font> | ||
value: <font color=indigo><''some-value''></font> | value: <font color=indigo><''some-value''></font> | ||
Line 33: | Line 37: | ||
name: <font color=indigo><''target-task-name''></font> | name: <font color=indigo><''target-task-name''></font> | ||
taskSpec: <font color=teal> # one of 'taskRef' and 'taskSpec' is required</font> | taskSpec: <font color=teal> # one of 'taskRef' and 'taskSpec' is required</font> | ||
[[# | taskRef: | ||
name: | |||
<span id='bundle'></span>[[Tekton_Bundle|bundle]]: | |||
[[#Pod_Template|podTemplate]]: | |||
schedulerName: <font color=indigo><''scheduler-name''></font> | schedulerName: <font color=indigo><''scheduler-name''></font> | ||
securityContext: | securityContext: | ||
Line 42: | Line 49: | ||
persistentVolumeClaim: | persistentVolumeClaim: | ||
claimName: <font color=indigo><''claim-name''></font> | claimName: <font color=indigo><''claim-name''></font> | ||
[[# | [[#Workspace|workspaces]]: | ||
- name: <font color=indigo><''workspace-name''></font> <font color=teal># must match workspace name in the Task</font> | - name: <font color=indigo><''workspace-name''></font> <font color=teal># must match workspace name in the Task</font> | ||
persistentVolumeClaim: | persistentVolumeClaim: | ||
claimName: <font color=indigo><''claim-name''> <font color=teal># the PVC must already exist</font> | claimName: <font color=indigo><''claim-name''> <font color=teal># the PVC must already exist</font> | ||
subPath: my-subdir | subPath: my-subdir | ||
[[# | [[#Sidecar|sidecars]]: | ||
- ... | - ... | ||
</font> | </font> | ||
=Specifying the Target Task= | |||
The target task can be specified either by reference, as shown [[#taskRef|above]], or embedding the task specification under <code>taskSpec</code>. | The target task can be specified either by reference, as shown [[#taskRef|above]], or embedding the task specification under <code>taskSpec</code>. | ||
=Remote Task= | |||
<font color=darkkhaki>TO PROCESS: https://tekton.dev/docs/pipelines/taskruns/#remote-tasks</font> | <font color=darkkhaki>TO PROCESS: https://tekton.dev/docs/pipelines/taskruns/#remote-tasks</font> | ||
= | =Parameters= | ||
{{ | {{Internal|Tekton_Parameters#TaskRun_Parameters|Tekton Parameters}} | ||
=Resources= | |||
= | |||
{{External|https://tekton.dev/docs/pipelines/taskruns/#specifying-resources}} | {{External|https://tekton.dev/docs/pipelines/taskruns/#specifying-resources}} | ||
[[#PipelineResource|PipelineResources]] are deprecated. This field is valid for alpha only. | [[Tekton_Concepts#PipelineResource|PipelineResources]] are deprecated. This field is valid for alpha only. | ||
<font color=darkkhaki>TO PROCESS.</font> | <font color=darkkhaki>TO PROCESS.</font> | ||
= | =Pod Template= | ||
{{External|https://tekton.dev/docs/pipelines/taskruns/#specifying-a-pod-template}} | {{External|https://tekton.dev/docs/pipelines/taskruns/#specifying-a-pod-template}} | ||
The pod template, if specifies, serves are the configuration starting point for the pod in which the container images specified by the task will execute. This permits customization of the pod configuration, to make it specific to this task run. | The pod template, if specifies, serves are the configuration starting point for the pod in which the container images specified by the task will execute. This permits customization of the pod configuration, to make it specific to this task run. | ||
<font color=darkkhaki>TO PROCESS.</font> | <font color=darkkhaki>TO PROCESS: | ||
= | * https://tekton.dev/docs/pipelines/podtemplates/ | ||
* https://tekton.dev/docs/pipelines/taskruns/#specifying-a-pod-template | |||
</font> | |||
=Workspace= | |||
{{External|https://tekton.dev/docs/pipelines/taskruns/#specifying-workspaces}} | {{External|https://tekton.dev/docs/pipelines/taskruns/#specifying-workspaces}} | ||
<font color=darkkhaki>TO PROCESS.</font> | <font color=darkkhaki>TO PROCESS.</font> | ||
= | =Sidecar= | ||
{{External|https://tekton.dev/docs/pipelines/taskruns/#specifying-sidecars}} | {{External|https://tekton.dev/docs/pipelines/taskruns/#specifying-sidecars}} | ||
<font color=darkkhaki>TO PROCESS.</font> | <font color=darkkhaki>TO PROCESS.</font> | ||
= | =Timeout= | ||
{{External|https://tekton.dev/docs/pipelines/taskruns/#configuring-the-failure-timeout}} | {{External|https://tekton.dev/docs/pipelines/taskruns/#configuring-the-failure-timeout}} | ||
<font color=darkkhaki>TO PROCESS.</font> | <font color=darkkhaki>TO PROCESS.</font> | ||
= | =Service Account= | ||
{{External|https://tekton.dev/docs/pipelines/taskruns/#specifying-serviceaccount-credentials}} | {{External|https://tekton.dev/docs/pipelines/taskruns/#specifying-serviceaccount-credentials}} | ||
<font color=darkkhaki>TO PROCESS: | <font color=darkkhaki>TO PROCESS: | ||
Line 98: | Line 93: | ||
</font> | </font> | ||
=TaskRun Life Cycle= | |||
<font color=darkkhaki>TO PROCESS: https://tekton.dev/docs/pipelines/taskruns/#monitoring-execution-status</font> | <font color=darkkhaki>TO PROCESS: https://tekton.dev/docs/pipelines/taskruns/#monitoring-execution-status</font> | ||
=TaskRun Operations= | |||
* [[Tekton_Operations#List_TaskRuns|List taskruns]] | * [[Tekton_Operations#List_TaskRuns|List taskruns]] | ||
* [[Tekton_Operations#Display_Execution_Log_of_a_TaskRun|Display execution log of a taskrun]] | * [[Tekton_Operations#Display_Execution_Log_of_a_TaskRun|Display execution log of a taskrun]] | ||
* [[Tekton_Operations#Cancel_TaskRuns|Cancel a taskrun]] | * [[Tekton_Operations#Cancel_TaskRuns|Cancel a taskrun]] |
Latest revision as of 04:22, 29 April 2022
External
- https://tekton.dev/docs/pipelines/taskruns/
- https://github.com/tektoncd/pipeline/blob/main/docs/taskruns.md
Internal
Overview
A task run (or taskRun) instantiates a specific task to execute on a particular set of inputs and produce a particular set of outputs, within specific conditions (for example, build flags). A task run connects resources with tasks. A task run can be created individually via CLI, by a pipeline run, as part of a pipeline, or by a Tekton components such as Tekton Triggers. The task run is implemented as a Kubernetes custom resource.
The task run can be used to parameterize the task. Specific values for task parameters can be declared in the task run.
Example
A simple taskrun example:
apiVersion: tekton.dev/v1beta1
kind: TaskRun
metadata:
name: hello-task-run
spec:
taskRef:
name: hello
Manifest
apiVersion: tekton.dev/v1beta1 # required field kind: TaskRun # required field metadata: # required field name: <taskrun-name> # required field spec: # required field params: - name: <parameter-name> value: <some-value> serviceAccountName: <service-account-name> taskRef: # one of 'taskRef' and 'taskSpec' is required name: <target-task-name> taskSpec: # one of 'taskRef' and 'taskSpec' is required taskRef: name: bundle: podTemplate: schedulerName: <scheduler-name> securityContext: runAsNonRoot: true runAsUser: 1001 volumes: - name: <volume-name> persistentVolumeClaim: claimName: <claim-name> workspaces: - name: <workspace-name> # must match workspace name in the Task persistentVolumeClaim: claimName: <claim-name> # the PVC must already exist subPath: my-subdir sidecars: - ...
Specifying the Target Task
The target task can be specified either by reference, as shown above, or embedding the task specification under taskSpec
.
Remote Task
TO PROCESS: https://tekton.dev/docs/pipelines/taskruns/#remote-tasks
Parameters
Resources
PipelineResources are deprecated. This field is valid for alpha only. TO PROCESS.
Pod Template
The pod template, if specifies, serves are the configuration starting point for the pod in which the container images specified by the task will execute. This permits customization of the pod configuration, to make it specific to this task run. TO PROCESS:
- https://tekton.dev/docs/pipelines/podtemplates/
- https://tekton.dev/docs/pipelines/taskruns/#specifying-a-pod-template
Workspace
TO PROCESS.
Sidecar
TO PROCESS.
Timeout
TO PROCESS.
Service Account
TO PROCESS:
- https://tekton.dev/docs/pipelines/taskruns/#specifying-serviceaccount-credentials
- https://tekton.dev/docs/pipelines/taskruns/#example-of-using-custom-serviceaccount-credentials
TaskRun Life Cycle
TO PROCESS: https://tekton.dev/docs/pipelines/taskruns/#monitoring-execution-status