Merge pull request #86324 from eromanova97/pipelines-rn-upstream

bergerhoffer · web-flow · commit b5b5ebf681f8 · 2024-12-18T10:42:23.000-05:00
OpenShift Pipelines release notes 1.17 (upstream)
diff --git a/modules/op-release-notes-1-17.adoc b/modules/op-release-notes-1-17.adoc
@@ -94,6 +94,10 @@ spec:
 # ...
 ----
 
+* With this update, after the execution of a pipeline run or task run, the YAML manifest of the resource contains a label showing the ID of the user who executed it. For a `PipelineRun` resource, the label is `tekton.dev/PipelineRunUID`. For a `TaskRun` resource, the label is `tekton.dev/TaskRunUID`.
+
+* With this update, when you use the `spec.pipeline,performance` spec in the `TektonConfig` CR to specify performance tuning values such as `threads-per-controller`, `kube-api-qps`, and `kube-api-burst`, {pipelines-shortname} applies these values to the resolver controller as well as the other controllers.
+
 [id="operator-new-features-1-17_{context}"]
 === Operator
 
@@ -105,17 +109,45 @@ spec:
 $ tkn task start skopeo-copy -p ARGS="--all --preserve-digests"
 ----
 
+* With this update, {pipelines-shortname} applies the ephemeral volume setting of any security context constraint (SCC) that you apply to a pipeline or task.
+
 [id="pac-new-features-1-17_{context}"]
 === {pac}
 
 * With this update, the `pipelines_as_code_running_pipelineruns_count` metric is added to show the number of running `PipelineRun` resources in {pac}. The metric can be filtered by repository or by namespace.
 
 * With this update, the `pipelines_as_code_pipelinerun_duration_seconds_sum` metric is added to show the total duration in seconds taken by all `PipelineRun` resources in {pac}. The metric can be filtered by repository, namespace, `PipelineRun` status, and `PipelineRun` status change reason.
 
+[id="tekton-results-new-features-1-17_{context}"]
+=== {tekton-results}
+
+* With this update, you can configure {tekton-results} to include certain labels and annotation from the YAML manifests of pipelines and tasks in the `summary fields` column in the results tables. By default, the value of the `tekton.dev/pipeline` label is used. To make this change, modify the `TektonResult` CR as shown in the following example:
++
+.Example of configuring summary labels and annotations in the `TektonResult` CR
+[source,yaml]
+----
+apiVersion: operator.tekton.dev/v1
+kind: TektonResult
+metadata:
+  name: result
+spec:
+     options:
+        deployments:
+           tekton-results-watcher:
+              spec:
+                  template:
+                     spec:
+                        containers:
+                        - name: watcher
+                          args:
+                          - "--summary_labels=org.tekton.sample_label,tekton.dev/pipeline"
+                          - "--summary_annotations=org.tekton.sample_annotation"
+----
+
 [id="tekton-chains-new-features-1-17_{context}"]
 === {tekton-chains}
 
-* With this update, you can configure the `TektonConfig` custom resource (CR) to generate the `x509` key pair of the `ecdsa` type and use it with {tekton-chains} to sign artifacts. You can generate the key pair by setting the the `generateSigningSecret` field in the `TektonConfig` custom resource (CR) to `true`:
+* With this update, you can configure the `TektonConfig` custom resource (CR) to generate the `x509` key pair of the `ecdsa` type and use it with {tekton-chains} to sign artifacts. You can generate the key pair by setting the `generateSigningSecret` field in the `TektonConfig` custom resource (CR) to `true`:
 +
 .Example of creating an `ecdsa` key pair
 [source,yaml]
@@ -164,7 +196,7 @@ spec:
 ====
 Before upgrading to {pipelines-shortname} 1.17, if you configured any pipelines that use `ClusterTask` resources, you must edit them to use the tasks in the `openshift-pipelines` namespace. Otherwise, after the upgrade, the pipelines will fail.
 
-For more information about using the tasks in the `openshift-pipelines` namespace, see xref:../create/remote-pipelines-tasks-resolvers.adoc#resolver-cluster-tasks-ref_remote-pipelines-tasks-resolvers[Tasks provided in the OpenShift Pipelines namespace].
+For more information about using the tasks in the `openshift-pipelines` namespace, see xref:../create/remote-pipelines-tasks-resolvers.adoc#resolver-cluster-tasks-ref_remote-pipelines-tasks-resolvers[Tasks provided in the {pipelines-shortname} namespace].
 ====
 
 * With this update, the community cluster tasks are removed from the Operator. As an alternative, you can download them from the link:https://github.com/tektoncd/catalog[Tekton catalog] (GitHub resource). The community cluster tasks are planned to be added as tasks in a future release. The following list shows the removed community cluster tasks:
@@ -192,3 +224,39 @@ For more information about using the tasks in the `openshift-pipelines` namespac
 * Before this update, running the `tkn pac create repo` command on an empty repository resulted in the `.` period symbol being generated as the name of the pipeline run in the template. With this update, the issue is fixed, and the `REPO_NAME.git` is now used as the pipeline run name.
 
 * With this update, the pipeline run failure handling is fixed to accurately report validation failures in the `status.message` field and consistently trigger `finally` tasks, even if a task fails the validation.
+
+* Before this update, when a pod failed because of an out-of-memory error, the task run did not immediately fail. Instead, it was unresponsive for some time and then failed. With this update, the task run immediately fails.
+
+* Before this update, if a `CustomRun` resource referred to a pipeline or task resource that returned an array as a result, a result type mismatch was reported in the log. With this update, the array result is processed correctly.
+
+* Before this update, when a task run failed, in some cases the statuses of some of the steps in the task were not recorded correctly in the `TaskRun` YAML manifesto. With this update, the statuses are correctly recorded. 
+
+* Before this update, if a step in a task failed, the subsequent steps were sometimes not marked as skipped in the YAML manifest of the task run or pipeline run. With this update, the steps are marked as skipped.
+
+* Before this update, if a pipeline run included a task that failed validation, a subsequent `finally` task did not run, even though it is expected to run after any failures of the previous tasks. With this update, the `finally` task runs.
+
+* Before this update, when using {pac} with GitLab, if the `.tekton` directory contained more than 20 files, some pipeline runs failed to start. With this update, the pipeline runs start correctly.
+
+* Before this update, when using {pac} with BitBucket, an incorrect payload in a BitBucket event could cause the {pac} controller to crash. With this update, the controller does not crash, validates payload before processing it, and correctly reports the error.
+
+* Before this update, when using {pac}, when you deleted a pipeline run before it was completed, temporary Git authentication secrets remained in the {OCP} namespace. Because of this issue, the quota for secrets could be reached, and in this case new pipeline runs failed to start. With this update, {pac} deletes temporary secrets properly.
+
+* Before this update, when using {pac} with BitBucket, tag-related events were not matched when a pipeline run was configured for `on-target-branch`, for example: `on-target-branch: [refs/tags/*]`. This happened because the BitBucket events payload related to a tag does not contain a `refs/tags` prefix. With this update, {pac} matches the tag events correctly.
+
+* Before this update, when a task run was canceled, {tekton-chains} did not record the specification of the task. With this update, {tekton-chains} records the specification of the task.
+
+* Before this update, in {tekton-chains}, the recorded steps in the specification of a task (`TaskRun.Status.steps`) could mismatch, even when the task run properly executed all steps in the task. With this update, the steps in the task specification and the steps executed in the task run are recorded correctly.
+
+* Before this update, when a pipeline run ended because of a timeout, the log output sometimes contained error messages that were not valid and the status of the pipeline run was not reported correctly. With this update, such messages do not appear in the log and the status is reported correctly.
+
+* Before this update, when you specified a workspace to be mounted in one or several steps of a task, {pipelines-shortname} mounted the workspace for all steps in the task. With this update, the workspace is mounted only in the steps where it is specified.
+
+* Before this update, when using {pac}, if the {OCP} cluster was very busy, some pipeline runs failed to execute because the concurrency queue was out of order and {pac} did not recover properly. With this update, {pac} properly manages the concurrency queue and executes all pipeline runs.
+
+* Before this update, if you specified default container resource requirements in the `TektonConfig` CR and then applied a `LimitRange` setting to a pipeline or task, the `LimitRange` setting was sometimes not applied because the default requirements overrode it. With this update, the `LimitRange` setting overrides the default container resource requirements.
+
+* Before this update, if a pipeline run or task run failed to execute because of a validation error, {pipelines-shortname} recorded and displayed a generic `Failed` status for the pipeline run or task run. With this update, {pipelines-shortname} records a `Failed Validation` status. 
+
+* Before this update, when you used the `tkn bundle` command to read the content of a large-sized Tekton bundle, the command might fail. With this update, the `tkn` command-line utilities correctly handles large Tekton bundles.
+
+* Before this update, when you used the `tkn` command-line utility to view a completed pipeline run, tasks that were skipped because of conditions you set up in the pipeline were displayed as `Succeeded(Completed)`. With this update, they are no longer displayed as completed. 
