Skip to content

Commit 2add788

Browse files
JSticklerJStickler
authored
Merge pull request #44706 from sounix000/3772-Pipelines-1-7-RN
RHDEVDOCS-3772 Release Notes for Pipelines 1.7 GA
2 parents c16f83e + 214f70a commit 2add788

File tree

4 files changed

+317
-11
lines changed

4 files changed

+317
-11
lines changed

‎_attributes/common-attributes.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ endif::[]
6969
//pipelines
7070
:pipelines-title: Red Hat OpenShift Pipelines
7171
:pipelines-shortname: Pipelines
72-
:pipelines-ver: pipelines-1.6
72+
:pipelines-ver: pipelines-1.7
7373
//odo
7474
:odo-title: odo
7575
//alibaba cloud

‎cicd/pipelines/op-release-notes.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,8 @@ include::modules/op-tkn-pipelines-compatibility-support-matrix.adoc[leveloffset=
2323
include::modules/making-open-source-more-inclusive.adoc[leveloffset=+1]
2424

2525
// Modules included, most to least recent
26+
include::modules/op-release-notes-1-7.adoc[leveloffset=+1]
27+
2628
include::modules/op-release-notes-1-6.adoc[leveloffset=+1]
2729

2830
include::modules/op-release-notes-1-5.adoc[leveloffset=+1]

‎modules/op-release-notes-1-7.adoc

Lines changed: 305 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,305 @@
1+
// Module included in the following assembly:
2+
//
3+
// * cicd/pipelines/op-release-notes.adoc
4+
:_content-type: REFERENCE
5+
[id="op-release-notes-1-7_{context}"]
6+
= Release notes for {pipelines-title} General Availability 1.7
7+
8+
With this update, {pipelines-title} General Availability (GA) 1.7 is available on {product-title} 4.10.
9+
10+
[id="new-features-1-7_{context}"]
11+
== New features
12+
13+
In addition to the fixes and stability improvements, the following sections highlight what is new in {pipelines-title} 1.7.
14+
15+
[id="pipelines-new-features-1-7_{context}"]
16+
=== Pipelines
17+
18+
* With this update, the `when` expressions in a `Task` object are scoped to guard the tasks by default. To continue guarding the `Task` object and its dependent tasks, set the `scope-when-expressions-to-task` flag to `true`.
19+
+
20+
[NOTE]
21+
====
22+
The `scope-when-expressions-to-task` flag is deprecated and will be removed in a future release. As a best practice for {pipelines-shortname}, use `when` expressions scoped to the guarded `Task` only.
23+
====
24+
// https://github.com/tektoncd/pipeline/pull/4580
25+
26+
* With this update, you can use variable substitution in the `subPath` field of a workspace within a task.
27+
// https://github.com/tektoncd/pipeline/pull/4351
28+
29+
* With this update, you can reference parameters and results by using a bracket notation with single or double quotes. Prior to this update, you could only use the dot notation. For example, the following are now equivalent:
30+
** `$(param.myparam)`, `$(param['myparam'])`, and `$(param["myparam"])`.
31+
+
32+
You can use single or double quotes to enclose parameter names that contain problematic characters, such as `"."`. For example, `$(param['my.param'])` and `$(param["my.param"])`.
33+
// https://github.com/tektoncd/pipeline/pull/4268
34+
35+
* With this update, you can include the the `onError` parameter of a step in the task definition without enabling the `enable-api-fields` flag.
36+
// https://github.com/tektoncd/pipeline/pull/4251
37+
38+
[id="triggers-new-features-1-7_{context}"]
39+
=== Triggers
40+
41+
* With this update, the `feature-flag-triggers` config map has a new field `labels-exclusion-pattern`. You can set the value of this field to a regular expression (regex) pattern. The controller filters out labels that match the regex pattern from propagating from the event listener to the resources created for the event listener.
42+
// https://github.com/tektoncd/triggers/pull/1227
43+
44+
* With this update, the `TriggerGroups` field is added to the `EventListener` specification. Using this field, you can specify a set of interceptors to run before selecting and running a group of triggers. To enable this feature, set the `enable-api-fields` flag in the `feature-flags-triggers` config map to `alpha`.
45+
// https://github.com/tektoncd/triggers/pull/1232
46+
47+
* With this update, `Trigger` resources support custom runs defined by a `TriggerTemplate` template.
48+
// https://github.com/tektoncd/triggers/pull/1283/files
49+
50+
* With this update, Triggers support emitting Kubernetes events from an `EventListener` pod.
51+
// https://github.com/tektoncd/triggers/pull/1222
52+
53+
* With this update, count metrics are available for the following objects: `ClusterInteceptor`, `EventListener`, `TriggerTemplate`, `ClusterTriggerBinding`, and `TriggerBinding`.
54+
// https://github.com/tektoncd/triggers/pull/1305
55+
56+
* This update adds the `ServicePort` specification to Kubernetes resource. You can use this specification to modify which port exposes the event listener service. The default port is `8080`.
57+
// https://github.com/tektoncd/triggers/pull/1272
58+
59+
* With this update, you can use the `targetURI` field in the `EventListener` specification to send cloud events during trigger processing. To enable this feature, set the `enable-api-fields` flag in the `feature-flags-triggers` config map to `alpha`.
60+
// https://github.com/tektoncd/triggers/pull/1259
61+
62+
* With this update, the `tekton-triggers-eventlistener-roles` object now has a `patch` verb, in addition to the `create` verb that already exists.
63+
// https://github.com/tektoncd/triggers/pull/1291
64+
65+
* With this update, the `securityContext.runAsUser` parameter is removed from event listener deployment.
66+
// https://github.com/tektoncd/triggers/pull/1213
67+
68+
[id="cli-new-features-1-7_{context}"]
69+
=== CLI
70+
71+
* With this update, the `tkn [pipeline | pipelinerun] export` command exports a pipeline or pipeline run as a YAML file. For example:
72+
** Export a pipeline named `test_pipeline` in the `openshift-pipelines` namespace:
73+
+
74+
[source,terminal]
75+
----
76+
$ tkn pipeline export test_pipeline -n openshift-pipelines
77+
----
78+
** Export a pipeline run named `test_pipeline_run` in the `openshift-pipelines` namespace:
79+
+
80+
[source,terminal]
81+
----
82+
$ tkn pipelinerun export test_pipeline_run -n openshift-pipelines
83+
----
84+
// https://github.com/tektoncd/cli/pull/1398 and https://github.com/tektoncd/cli/pull/1500
85+
86+
* With this update, the `--grace` option is added to the `tkn pipelinerun cancel`. Use the `--grace` option to terminate a pipeline run gracefully instead of forcing the termination. To enable this feature, set the `enable-api-fields` flag in the `feature-flags` config map to `alpha`.
87+
// https://github.com/tektoncd/cli/pull/1479
88+
89+
* This update adds the Operator and Chains versions to the output of the `tkn version` command.
90+
+
91+
[IMPORTANT]
92+
====
93+
Tekton Chains is a Technology Preview feature.
94+
====
95+
// https://github.com/tektoncd/cli/pull/1486 and https://github.com/tektoncd/cli/pull/1509
96+
97+
* With this update, the `tkn pipelinerun describe` command displays all canceled task runs, when you cancel a pipeline run. Before this fix, only one task run was displayed.
98+
// https://github.com/tektoncd/cli/pull/1482
99+
100+
* With this update, you can skip supplying the asking specifications for optional workspace when you run the `tkn [t | p | ct] start` command skips with the `--skip-optional-workspace` flag. You can also skip it when running in interactive mode.
101+
// https://github.com/tektoncd/cli/pull/1465
102+
103+
* With this update, you can use the `tkn chains` command to manage Tekton Chains. You can also use the `--chains-namespace` option to specify the namespace where you want to install Tekton Chains.
104+
+
105+
[IMPORTANT]
106+
====
107+
Tekton Chains is a Technology Preview feature.
108+
====
109+
// https://github.com/tektoncd/cli/pull/1440 and https://github.com/tektoncd/cli/pull/1522
110+
111+
[id="operator-new-features-1-7_{context}"]
112+
=== Operator
113+
114+
* With this update, you can use the {pipelines-title} Operator to install and deploy Tekton Hub and Tekton Chains.
115+
+
116+
[IMPORTANT]
117+
====
118+
Tekton Chains and and deployment of Tekton Hub on a cluster are Technology Preview features.
119+
====
120+
// https://github.com/tektoncd/operator/pull/467, https://github.com/tektoncd/operator/pull/479, https://github.com/tektoncd/operator/pull/467, https://github.com/tektoncd/operator/pull/630, and https://github.com/tektoncd/operator/pull/630
121+
122+
* With this update, you can find and use Pipelines as Code (PAC) as an add-on option.
123+
+
124+
[IMPORTANT]
125+
====
126+
Pipelines as Code is a Technology Preview feature.
127+
====
128+
// https://github.com/tektoncd/operator/pull/550
129+
130+
* With this update, you can now disable the installation of community cluster tasks by setting the `communityClusterTasks` parameter to `false`. For example:
131+
+
132+
[source,yaml]
133+
----
134+
...
135+
spec:
136+
profile: all
137+
targetNamespace: openshift-pipelines
138+
addon:
139+
params:
140+
- name: clusterTasks
141+
value: "true"
142+
- name: pipelineTemplates
143+
value: "true"
144+
- name: communityClusterTasks
145+
value: "false"
146+
...
147+
----
148+
// https://github.com/tektoncd/operator/pull/658
149+
150+
* With this update, you can disable the integration of Tekton Hub with the **Developer** perspective by setting the `enable-devconsole-integration` flag in the `TektonConfig` custom resource to `false`. For example:
151+
+
152+
[source,yaml]
153+
----
154+
...
155+
hub:
156+
params:
157+
- name: enable-devconsole-integration
158+
value: "true"
159+
...
160+
----
161+
// https://github.com/tektoncd/operator/pull/569
162+
163+
* With this update, the `operator-config.yaml` config map enables the output of the `tkn version` command to display of the Operator version.
164+
// https://github.com/tektoncd/operator/pull/563
165+
166+
* With this update, the version of the `argocd-task-sync-and-wait` tasks is modified to `v0.2`.
167+
// https://github.com/tektoncd/operator/pull/642
168+
169+
* With this update to the `TektonConfig` CRD, the `oc get tektonconfig` command displays the OPerator version.
170+
// https://github.com/tektoncd/operator/pull/644
171+
172+
* With this update, service monitor is added to the Triggers metrics.
173+
// https://github.com/tektoncd/operator/pull/635
174+
175+
[id="hub-new-features-1-7_{context}"]
176+
=== Hub
177+
178+
[IMPORTANT]
179+
====
180+
Deploying Tekton Hub on a cluster is a Technology Preview feature.
181+
====
182+
183+
Tekton Hub helps you discover, search, and share reusable tasks and pipelines for your CI/CD workflows. A public instance of Tekton Hub is available at link:https://hub.tekton.dev/[hub.tekton.dev].
184+
185+
Staring with {pipelines-title} 1.7, cluster administrators can also install and deploy a custom instance of Tekton Hub on enterprise clusters. You can curate a catalog with reusable tasks and pipelines specific to your organization.
186+
187+
[id="chains-new-features-1-7_{context}"]
188+
=== Chains
189+
190+
[IMPORTANT]
191+
====
192+
Tekton Chains is a Technology Preview feature.
193+
====
194+
195+
Tekton Chains is a Kubernetes Custom Resource Definition (CRD) controller. You can use it to manage the supply chain security of the tasks and pipelines created using {pipelines-title}.
196+
197+
By default, Tekton Chains monitors the task runs in your {product-title} cluster. Chains takes snapshots of completed task runs, converts them to one or more standard payload formats, and signs and stores all artifacts.
198+
199+
Tekton Chains supports the following features:
200+
201+
* You can sign task runs, task run results, and OCI registry images with cryptographic key types and services such as `cosign`.
202+
203+
* You can use attestation formats such as `in-toto`.
204+
205+
* You can securely store signatures and signed artifacts using OCI repository as a storage backend.
206+
207+
[id="pac-new-features-1-7_{context}"]
208+
=== Pipelines as Code (PAC)
209+
210+
[IMPORTANT]
211+
====
212+
Pipelines as Code is a Technology Preview feature.
213+
====
214+
215+
With Pipelines as Code, cluster administrators and users with the required privileges can define pipeline templates as part of source code Git repositories. When triggered by a source code push or a pull request for the configured Git repository, the feature runs the pipeline and reports status.
216+
217+
Pipelines as Code supports the following features:
218+
219+
* Pull request status. When iterating over a pull request, the status and control of the pull request is exercised on the platform hosting the Git repository.
220+
221+
* GitHub checks the API to set the status of a pipeline run, including rechecks.
222+
223+
* GitHub pull request and commit events.
224+
225+
* Pull request actions in comments, such as `/retest`.
226+
227+
* Git events filtering, and a separate pipeline for each event.
228+
229+
* Automatic task resolution in {pipelines-shortname} for local tasks, Tekton Hub, and remote URLs.
230+
231+
* Use of GitHub blobs and objects API for retrieving configurations.
232+
233+
* Access Control List (ACL) over a GitHub organization, or using a Prow-style `OWNER` file.
234+
235+
* The `tkn-pac` plugin for the `tkn` CLI tool, which you can use to manage {pac} repositories and bootstrapping.
236+
237+
* Support for GitHub Application, GitHub Webhook, Bitbucket Server, and Bitbucket Cloud.
238+
239+
[id="deprecated-features-1-7_{context}"]
240+
== Deprecated features
241+
242+
// Pipelines
243+
* Breaking change: The `disable-working-directory-overwrite` and `disable-home-env-overwrite` fields in the `TektonConfig` custom resource (CR) is removed. As a result, the `$HOME` environment variable and `workingDir` parameter are unavailable.
244+
// https://github.com/tektoncd/pipeline/pull/4587
245+
246+
* The `Conditions` custom resource definition (CRD) type is deprecated and planned to be removed in a future release. Instead, use the recommended `When` expression.
247+
// issue # unknown; discussed in Slack.
248+
249+
// Triggers
250+
* Breaking change: The `Triggers` resource validates the templates and generates an error if you do not specify the `EventListener` and `TriggerBinding` values.
251+
// https://github.com/tektoncd/triggers/pull/1277 and https://github.com/tektoncd/triggers/pull/1264
252+
253+
254+
[id="known-issues-1-7_{context}"]
255+
== Known issues
256+
257+
// Pipelines
258+
* Implicit parameter mapping incorrectly passes parameters from the top-level `Pipeline` or `PipelineRun` definitions to the `taskRef` tasks. Mapping should only occur from a top-level resource to tasks with in-line `taskSpec` specifications. This issue only affects users who have set the `enable-api-fields` feature flag to `alpha`.
259+
260+
261+
[id="fixed-issues-1-7_{context}"]
262+
== Fixed issues
263+
264+
// Pipelines
265+
* With this update, metadata such as `labels` and `annotations` from task and pipeline definitions does not propagate to task runs and pipeline runs.
266+
// https://github.com/tektoncd/pipeline/pull/4478
267+
268+
* With this update, if the `timeouts.tasks` field or the `timeouts.finally` field is set to `0`, then the `timeouts.pipeline` is also set to `0`.
269+
// https://github.com/tektoncd/pipeline/pull/4539
270+
271+
* With this update, the `-x` set flag is removed from scripts that do not use a shebang. The fix reduces potential data leak from script execution.
272+
// https://github.com/tektoncd/pipeline/pull/4451
273+
274+
* With this update, any backslash character present in the usernames in Git credentials is escaped with an additional backslash in the `.gitconfig` file.
275+
// https://github.com/tektoncd/pipeline/pull/4337
276+
277+
// Triggers
278+
* With this update, the `finalizer` property of the `EventListener` object is not necessary for cleaning up logging and config maps.
279+
// https://github.com/tektoncd/triggers/pull/1244
280+
281+
* With this update, the default HTTP client associated with the event listener server is removed, and a custom HTTP client added. As a result, the timeouts have improved.
282+
// https://github.com/tektoncd/triggers/pull/1308
283+
284+
* With this update, the Triggers cluster role now works with owner references.
285+
// https://github.com/tektoncd/triggers/pull/1267
286+
287+
* With this update, the race condition in the event listener does not happen when multiple interceptors return extensions.
288+
// https://github.com/tektoncd/triggers/pull/1282
289+
290+
// CLI
291+
* With this update, the `tkn pr delete` command does not delete the pipeline runs with the `ignore-running` flag.
292+
// https://github.com/tektoncd/cli/pull/1532
293+
294+
// Operator
295+
* With this update, the Operator pods do not continue restarting when you modify any add-on parameters.
296+
// https://github.com/tektoncd/operator/pull/631
297+
298+
* With this update, the `tkn serve` CLI pod is scheduled on infra nodes, if not configured in the subscription and config custom resources.
299+
// https://github.com/tektoncd/operator/pull/544
300+
301+
* With this update, cluster tasks with specified versions are not deleted during upgrade.
302+
// https://github.com/tektoncd/operator/pull/599
303+
304+
305+

‎modules/op-tkn-pipelines-compatibility-support-matrix.adoc

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -13,19 +13,18 @@ GA:: General Availability
1313
[options="header"]
1414
|===
1515

16-
| {pipelines-title} Version 4+| Component Version | OpenShift Version | Support Status
16+
| {pipelines-title} Version 7+| Component Version | OpenShift Version | Support Status
1717

18-
|Operator | Pipelines | Triggers | CLI | Catalog | |
18+
| Operator | Pipelines | Triggers | CLI | Catalog | Chains | Hub | PAC | |
1919

20-
|1.6 | 0.28.x | 0.16.x | 0.21.x | 0.28 | 4.9 | GA
21-
|1.5 | 0.24.x | 0.14.x | 0.19.x | 0.24 | 4.8 | GA
22-
|1.4 | 0.22.x | 0.12.x | 0.17.x | 0.22 | 4.7 | GA
20+
|1.7 | 0.33.x | 0.19.x | 0.23.x | 0.33 | 0.8.0 (TP) | 1.7.0 (TP) | 0.5.4 (TP) | 4.9, 4.10 | GA
2321

24-
|===
22+
|1.6 | 0.28.x | 0.16.x | 0.21.x | 0.28 | N/A | N/A | N/A | 4.9 | GA
23+
24+
|1.5 | 0.24.x | 0.14.x (TP) | 0.19.x | 0.24 | N/A | N/A | N/A | 4.8 | GA
2525

26-
[NOTE]
27-
====
28-
In {pipelines-title} 1.6, Triggers 0.16.x transitioned to GA status. In earlier versions, Triggers was available as a technology preview feature.
29-
====
26+
|1.4 | 0.22.x | 0.12.x (TP) | 0.17.x | 0.22 | N/A | N/A | N/A | 4.7 | GA
27+
28+
|===
3029

3130
For questions and feedback, you can send an email to the product team at [email protected].

0 commit comments

Comments
 (0)