You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/op-about-tasks.adoc
+25-7Lines changed: 25 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,11 +5,11 @@
5
5
[id="about-tasks_{context}"]
6
6
= Tasks
7
7
8
-
_Tasks_ are the building blocks of a Pipeline and consists of sequentially executed steps. It is essentially a function of inputs and outputs. A Task can run individually or as a part of the pipeline. Tasks are reusable and can be used in multiple Pipelines.
8
+
_Tasks_ are the building blocks of a pipeline and consists of sequentially executed steps. It is essentially a function of inputs and outputs. A task can run individually or as a part of the pipeline. Tasks are reusable and can be used in multiple Pipelines.
9
9
10
-
_Steps_ are a series of commands that are sequentially executed by the Task and achieve a specific goal, such as building an image. Every Task runs as a pod, and each Step runs as a container within that pod. Because Steps run within the same pod, they can access the same volumes for caching files, config maps, and secrets.
10
+
_Steps_ are a series of commands that are sequentially executed by the task and achieve a specific goal, such as building an image. Every task runs as a pod, and each step runs as a container within that pod. Because steps run within the same pod, they can access the same volumes for caching files, config maps, and secrets.
11
11
12
-
The following example shows the `apply-manifests` Task.
12
+
The following example shows the `apply-manifests` task.
13
13
14
14
[source,yaml]
15
15
----
@@ -36,9 +36,27 @@ spec: <4>
36
36
oc apply -f $(params.manifest_dir)
37
37
echo -----------------------------------
38
38
----
39
-
<1> The Task API version, `v1beta1`.
39
+
<1> The task API version, `v1beta1`.
40
40
<2> The type of Kubernetes object, `Task`.
41
-
<3> The unique name of this Task.
42
-
<4> The list of parameters and Steps in the Task and the workspace used by the Task.
41
+
<3> The unique name of this task.
42
+
<4> The list of parameters and steps in the task and the workspace used by the task.
43
43
44
-
This Task starts the pod and runs a container inside that pod using the specified image to run the specified commands.
44
+
This task starts the pod and runs a container inside that pod using the specified image to run the specified commands.
45
+
46
+
[NOTE]
47
+
====
48
+
Starting with {pipelines-shortname} 1.6, the following defaults from the step YAML file are removed:
49
+
50
+
* The `HOME` environment variable does not default to the `/tekton/home` directory
51
+
* The `workingDir` field does not default to the `/workspace` directory
52
+
53
+
Instead, the container for the step defines the `HOME` environment variable and the `workingDir` field. However, you can override the default values by specifying the custom values in the YAML file for the step.
54
+
55
+
As a temporary measure, to maintain backward compatibility with the older {pipelines-shortname} versions, you can set the following fields in the `TektonConfig` custom resource definition to `false`:
0 commit comments