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
A _PipelineRun_ is the running instance of a Pipeline. It instantiates a Pipeline for execution with specific inputs, outputs, and execution parameters on a cluster. A corresponding TaskRun is created for each Task automatically in the PipelineRun.
8
+
A _pipeline run_ is the running instance of a pipeline. It instantiates a pipeline for execution with specific inputs, outputs, and execution parameters on a cluster. A corresponding task run is created for each task automatically in the pipeline run.
9
9
10
-
All the Tasks in the Pipeline are executed in the defined sequence until all Tasks are successful or a Task fails. The `status` field tracks and stores the progress of each TaskRun in the PipelineRun for monitoring and auditing purpose.
10
+
All the tasks in the pipeline are executed in the defined sequence until all tasks are successful or a task fails. The `status` field tracks and stores the progress of each task run in the pipeline run for monitoring and auditing purpose.
11
11
12
-
The following example shows a PipelineRun to run the `build-and-deploy` Pipeline with relevant resources and parameters:
12
+
The following example runs the `build-and-deploy` pipeline with relevant resources and parameters:
13
13
[source,yaml]
14
14
----
15
15
apiVersion: tekton.dev/v1beta1 <1>
@@ -36,9 +36,9 @@ spec:
36
36
requests:
37
37
storage: 500Mi
38
38
----
39
-
<1> PipelineRun API version `v1beta1`.
39
+
<1> Pipeline run API version `v1beta1`.
40
40
<2> Specifies the type of Kubernetes object. In this example, `PipelineRun`.
41
-
<3> Unique name to identify this PipelineRun.
42
-
<4> Name of the Pipeline to be run. In this example, `build-and-deploy`.
43
-
<5> Specifies the list of parameters required to run the Pipeline.
44
-
<6> Workspace used by the PipelineRun.
41
+
<3> Unique name to identify this pipeline run.
42
+
<4> Name of the pipeline to be run. In this example, `build-and-deploy`.
43
+
<5> Specifies the list of parameters required to run the pipeline.
Copy file name to clipboardExpand all lines: modules/op-about-triggers.adoc
+11-11Lines changed: 11 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ The following example shows a code snippet of the `TriggerBinding` resource, whi
18
18
+
19
19
[source,yaml]
20
20
----
21
-
apiVersion: triggers.tekton.dev/v1alpha1 <1>
21
+
apiVersion: triggers.tekton.dev/v1beta1 <1>
22
22
kind: TriggerBinding <2>
23
23
metadata:
24
24
name: vote-app <3>
@@ -32,7 +32,7 @@ spec:
32
32
value: $(body.head_commit.id)
33
33
----
34
34
+
35
-
<1> The API version of the `TriggerBinding` resource. In this example, `v1alpha1`.
35
+
<1> The API version of the `TriggerBinding` resource. In this example, `v1beta1`.
36
36
<2> Specifies the type of Kubernetes object. In this example, `TriggerBinding`.
37
37
<3> Unique name to identify the `TriggerBinding` resource.
38
38
<4> List of parameters which will be extracted from the received event payload and passed to the `TriggerTemplate` resource. In this example, the Git repository URL, name, and revision are extracted from the body of the event payload.
@@ -44,7 +44,7 @@ The following example shows a code snippet of a `TriggerTemplate` resource, whic
44
44
+
45
45
[source,yaml,subs="attributes+"]
46
46
----
47
-
apiVersion: triggers.tekton.dev/v1alpha1 <1>
47
+
apiVersion: triggers.tekton.dev/v1beta1 <1>
48
48
kind: TriggerTemplate <2>
49
49
metadata:
50
50
name: vote-app <3>
@@ -87,13 +87,13 @@ spec:
87
87
storage: 500Mi
88
88
----
89
89
+
90
-
<1> The API version of the `TriggerTemplate` resource. In this example, `v1alpha1`.
90
+
<1> The API version of the `TriggerTemplate` resource. In this example, `v1beta1`.
91
91
<2> Specifies the type of Kubernetes object. In this example, `TriggerTemplate`.
92
92
<3> Unique name to identify the `TriggerTemplate` resource.
93
93
<4> Parameters supplied by the `TriggerBinding` resource.
94
94
<5> List of templates that specify the way resources must be created using the parameters received through the `TriggerBinding` or `EventListener` resources.
95
95
96
-
* The `Trigger` resource combines the `TriggerBinding` and `TriggerTemplate` resources, and optionally, the `interceptors` event processor.
96
+
* The `Trigger` resource combines the `TriggerBinding` and `TriggerTemplate` resources, and optionally, the `interceptors` event processor.
97
97
+
98
98
Interceptors process all the events for a specific platform that runs before the `TriggerBinding` resource. You can use interceptors to filter the payload, verify events, define and test trigger conditions, and implement other useful processing. Interceptors use secret for event verification. After the event data passes through an interceptor, it then goes to the trigger before you pass the payload data to the trigger binding. You can also use an interceptor to modify the behavior of the associated trigger referenced in the `EventListener` specification.
99
99
//image::op-triggers.png[]
@@ -102,7 +102,7 @@ The following example shows a code snippet of a `Trigger` resource, named `vote-
102
102
+
103
103
[source,yaml]
104
104
----
105
-
apiVersion: triggers.tekton.dev/v1alpha1 <1>
105
+
apiVersion: triggers.tekton.dev/v1beta1 <1>
106
106
kind: Trigger <2>
107
107
metadata:
108
108
name: vote-trigger <3>
@@ -112,11 +112,11 @@ spec:
112
112
- ref:
113
113
name: "github" <5>
114
114
params: <6>
115
-
- name: "secretRef"
115
+
- name: "secretRef"
116
116
value:
117
117
secretName: github-secret
118
118
secretKey: secretToken
119
-
- name: "eventTypes"
119
+
- name: "eventTypes"
120
120
value: ["push"]
121
121
bindings:
122
122
- ref: vote-app <7>
@@ -132,7 +132,7 @@ stringData:
132
132
secretToken: "1234567"
133
133
----
134
134
+
135
-
<1> The API version of the `Trigger` resource. In this example, `v1alpha1`.
135
+
<1> The API version of the `Trigger` resource. In this example, `v1beta1`.
136
136
<2> Specifies the type of Kubernetes object. In this example, `Trigger`.
137
137
<3> Unique name to identify the `Trigger` resource.
138
138
<4> Service account name to be used.
@@ -148,7 +148,7 @@ The following example shows an `EventListener` resource, which references the `T
148
148
+
149
149
[source,yaml]
150
150
----
151
-
apiVersion: triggers.tekton.dev/v1alpha1 <1>
151
+
apiVersion: triggers.tekton.dev/v1beta1 <1>
152
152
kind: EventListener <2>
153
153
metadata:
154
154
name: vote-app <3>
@@ -158,7 +158,7 @@ spec:
158
158
- triggerRef: vote-trigger <5>
159
159
----
160
160
+
161
-
<1> The API version of the `EventListener` resource. In this example, `v1alpha1`.
161
+
<1> The API version of the `EventListener` resource. In this example, `v1beta1`.
162
162
<2> Specifies the type of Kubernetes object. In this example, `EventListener`.
163
163
<3> Unique name to identify the `EventListener` resource.
0 commit comments