Merge pull request #84654 from mramendi/pipelines-1.16.1-rn

Author: adellape

modules/op-release-notes-1-16.adoc

@@ -35,17 +35,17 @@ spec:
                 containers:
                 - name: tekton-pipelines-controller
                   args:
-                    - "-resync-period=24h" 
+                    - "-resync-period=24h"
 # ...
 ----
 
-* With this update, when defining a pipeline, you can set the `onError` parameter for a task to `continue`. If you make this setting and the task fails when the pipeline is executed, the pipeline logs the error and continues to the next task. By default, a pipeline fails if a task in it fails. 
+* With this update, when defining a pipeline, you can set the `onError` parameter for a task to `continue`. If you make this setting and the task fails when the pipeline is executed, the pipeline logs the error and continues to the next task. By default, a pipeline fails if a task in it fails.
 +
 .Example of setting the `onError` parameter. After the `task-that-fails` task fails, the `next-task` executes
 [source,yaml]
 ----
-apiVersion: tekton.dev/v1 
-kind: Pipeline 
+apiVersion: tekton.dev/v1
+kind: Pipeline
 metadata:
   name: example-onerror-pipeline
 spec:
@@ -62,7 +62,7 @@ spec:
 # ...
 ----
 
-* With this update, if a task fails, a `finally` task can access the `reason` parameter in addition to the `status` parameter to distinguish if the failure was allowed or not. You can access the `reason` parameter  through `$(tasks.<task_name>.reason)`. If the failure is allowed, the `reason` is set to `FailureIgnored`. If the failure is not allowed, the `reason` is set to `Failed`. This additional information can be used to identify that the checks failed, but the failure can be ignored. 
+* With this update, if a task fails, a `finally` task can access the `reason` parameter in addition to the `status` parameter to distinguish if the failure was allowed or not. You can access the `reason` parameter  through `$(tasks.<task_name>.reason)`. If the failure is allowed, the `reason` is set to `FailureIgnored`. If the failure is not allowed, the `reason` is set to `Failed`. This additional information can be used to identify that the checks failed, but the failure can be ignored.
 
 * With this update, larger results are supported through sidecar logs as an alternative to the default configuration, which limits results to the size of 4 KB per step and 12 KB per task run. To enable larger results using sidecar logs, set the `pipeline.options.configMaps.feature-flags.data.results-from` spec to `sidecar-logs` in the `TektonConfig` CR.
 +
@@ -83,7 +83,7 @@ spec:
 # ...
 ----
 
-* Before this update, parameter propagation was allowed in `PipelineRun` and `TaskRun` resources, but not in the `Pipeline` resource. With this update, you can propagate `params` in the `Pipeline` resource down to the inlined pipeline `tasks` and its inlined `steps`. Wherever a resource, such as `PipelineTask` or `StepAction`, is referenced, you must pass the parameters explicitly. 
+* Before this update, parameter propagation was allowed in `PipelineRun` and `TaskRun` resources, but not in the `Pipeline` resource. With this update, you can propagate `params` in the `Pipeline` resource down to the inlined pipeline `tasks` and its inlined `steps`. Wherever a resource, such as `PipelineTask` or `StepAction`, is referenced, you must pass the parameters explicitly.
 +
 .Example of using `params` within a pipeline
 [source,yaml]
@@ -115,11 +115,11 @@ spec:
               name: step-action-echo
             params:
               - name: msg
-                value: "$(params.BYE)" 
+                value: "$(params.BYE)"
 # ...
 ----
 
-* With this update, you can use the task run or pipeline run definition to configure the compute resources for steps and sidecars in a task. 
+* With this update, you can use the task run or pipeline run definition to configure the compute resources for steps and sidecars in a task.
 +
 .Example task for configuring resources
 [source,yaml]
@@ -242,7 +242,7 @@ spec:
     options:
       disabled: false
       configMaps:
-        config-defaults-triggers: 
+        config-defaults-triggers:
           data:
             default-run-as-non-root: "true"
             default-run-as-user: "65532"
@@ -255,7 +255,7 @@ Optionally, you can set the values of the `default-run-as-user` and `default-run
 +
 You can also set the `default-fs-group` parameter to define the `fsGroup` value for the pod security context, which is the group ID that the container processes use for the file system. If you use an empty value, the default group ID of `65532` is used.
 
-* With this update, in triggers, the `EventListener` pod template now includes `securityContext` settings. Under these settings, you can configure `seccompProfile`, `runAsUser`, `runAsGroup`, and `fsGroup` parameters when the `el-security-context` flag is set to `true`. 
+* With this update, in triggers, the `EventListener` pod template now includes `securityContext` settings. Under these settings, you can configure `seccompProfile`, `runAsUser`, `runAsGroup`, and `fsGroup` parameters when the `el-security-context` flag is set to `true`.
 
 [id="web-console-new-features-1-16_{context}"]
 === Web console
@@ -264,7 +264,7 @@ You can also set the `default-fs-group` parameter to define the `fsGroup` value
 
 * With this update, the pipeline run and task run *list* pages in the web console now have a filter for the data source, such as `k8s` and `TektonResults API`.
 
-* Before this update, when using the web console in the *Developer* perspective, you could not specify the timeout for pipeline runs. With this update, you can set a timeout while starting the pipeline run in the *Developer* perspective of the web console. 
+* Before this update, when using the web console in the *Developer* perspective, you could not specify the timeout for pipeline runs. With this update, you can set a timeout while starting the pipeline run in the *Developer* perspective of the web console.
 
 * Before this update, the *Overview* pipeline dashboard only appeared when {tekton-results} was enabled. All the statistics came from only the Results API. With this update, the *Overview* pipeline dashboard is available regardless of whether {tekton-results} is enabled or not. When {tekton-results} is disabled, you can use the dashboard to see the statistics for objects in the cluster.
 
@@ -295,7 +295,7 @@ You can also set the `default-fs-group` parameter to define the `fsGroup` value
 [source,terminal]
 ----
 $ oc create secret generic mongo-url -n tekton-chains \ #
-  --from-file=MONGO_SERVER_URL=/home/user/MONGO_SERVER_URL 
+  --from-file=MONGO_SERVER_URL=/home/user/MONGO_SERVER_URL
 ----
 +
 .Example of configuring the `MONGO_SERVER_URL` value using a secret
@@ -387,7 +387,7 @@ spec:
               spec:
                 containers:
                 - args:
-                  - --namespace=dev, test 
+                  - --namespace=dev, test
                   name: tekton-chains-controller
 # ...
 ----
@@ -582,7 +582,7 @@ spec:
 
 * Before this update, when you uninstalled {tekton-hub} by deleting the `TektonHub` CR, the pod of the `hub-db-migration` job was not deleted. With this update, uninstalling {tekton-hub} deletes the pod.
 
-* Before this update, when you used {tekton-results} to store pod logs from pipelines and tasks, the operation to store the logs sometimes failed. The logs would include the `UpdateLog` action failing with the `canceled context` error. With this update, the operation completes correctly. 
+* Before this update, when you used {tekton-results} to store pod logs from pipelines and tasks, the operation to store the logs sometimes failed. The logs would include the `UpdateLog` action failing with the `canceled context` error. With this update, the operation completes correctly.
 
 * Before this update, when you passed a parameter value to a pipeline or task and the value included more than one variable with both full and short reference formats, for example, `$(tasks.task-name.results.variable1) + $(variable2)`, {pipelines-shortname} did not interpret the value correctly. The pipeline run or task run could stop execution and the Pipelines controller could crash. With this update, {pipelines-shortname} interprets the value correctly and the pipeline run or task run completes.
 
@@ -602,14 +602,34 @@ spec:
 
 * Before this update, if a step action parameter was an `array` type but a `string` value was passed in a task, there was no error indicating inconsistent parameter types and the default parameter value was used instead. With this update, an error is added to indicate the inconsistent values: `invalid parameter substitution: %s. Please check the types of the default value and the passed value`.
 
-* Before this update, task runs and pipeline runs were deleted by an external pruner when logs were streamed through the watcher. With this update, a finalizer is added to {tekton-results} for `TaskRun` and `PipelineRun` objects to ensure that the runs are stored and not deleted. The runs are stored either as records or until the deadline has passed, which is calculated as the completion time plus the `store_deadline` time. The finalizer does not prevent deletion if legacy log streaming from the watcher or pruner is enabled. 
+* Before this update, task runs and pipeline runs were deleted by an external pruner when logs were streamed through the watcher. With this update, a finalizer is added to {tekton-results} for `TaskRun` and `PipelineRun` objects to ensure that the runs are stored and not deleted. The runs are stored either as records or until the deadline has passed, which is calculated as the completion time plus the `store_deadline` time. The finalizer does not prevent deletion if legacy log streaming from the watcher or pruner is enabled.
 
-* Before this update, the web console supported the `v1beta1` API format to display the `TaskRun` and `PipelineRun` object records that are stored in {tekton-results}. With this update, the console supports the `v1` API format to display `TaskRun` and `PipelineRun` object records stored in {tekton-results}. 
+* Before this update, the web console supported the `v1beta1` API format to display the `TaskRun` and `PipelineRun` object records that are stored in {tekton-results}. With this update, the console supports the `v1` API format to display `TaskRun` and `PipelineRun` object records stored in {tekton-results}.
 
 * Before this update, when using {pac}, if different `PipelineRun` definitions used the same task name but different versions, for example when fetching tasks from {tekton-hub},the wrong version was sometimes triggered, because {pac} used the same task version for all pipeline runs. With this update, {pac} triggers the correct version of the referenced task.
 
 * Before this update, when you used a resolver to reference remote pipelines or tasks, transient communication errors caused immediate failure retrieving those remote references. With this update, the resolver requeues the retrieval and eventually retries the retrieval.
 
 * Before this update, {tekton-results} could use an increasing amount of memory when storing log information for pipeline runs and task runs. This update fixes the memory leak and {tekton-results} uses a normal amount of memory.
 
-* Before this update, when using {pac}, if your `.tekton` directory contained a pipeline that was not referenced by any `PipelineRun` definition triggered in the event, {pac} attempted to fetch all the required tasks for that pipeline even though it was not run. With this update, {pac} does not try to resolve pipelines that are not referenced in any pipeline run triggered by the current event.
+* Before this update, when using {pac}, if your `.tekton` directory contained a pipeline that was not referenced by any `PipelineRun` definition triggered in the event, {pac} attempted to fetch all the required tasks for that pipeline even though it was not run. With this update, {pac} does not try to resolve pipelines that are not referenced in any pipeline run triggered by the current event.
+
+[id="release-notes-1-16-1_{context}"]
+== Release notes for {pipelines-title} General Availability 1.16.1
+
+With this update, {pipelines-title} General Availability (GA) 1.16.1 is available on {OCP} 4.15 and later versions.
+
+[id="fixed-issues-1-16-1_{context}"]
+=== Fixed issues
+
+* Before this update, in the *Pipelines overview* page of the web console, users that do not have access to all namespaces could select *All* in the *Projects* list. The console displayed wrong information for that selection, because the statistics for some of the namespaces were not available to the user. With this update, users who do not have access to all namespaces cannot select *All* in the *Projects* list.
+
+* Before this update, when you tried to used the web console to start a pipeline or task that defined a parameter of the type `array`, entering a value for this parameter resulted in an error and you could not start the pipeline or task. With this update, you can use the web console to start a pipeline or task that defines a parameter of the type `array` and entering a value for this parameter works normally.
+
+* Before this update, when using {pac} with a Bitbucket Git repository, the {pac} controller sometimes crashed and a `panic: runtime error: invalid memory address or nil pointer dereference` message was logged. With this update, the {pac} controller does not crash.
+
+* Before this update, when using {tekton-results}, the `tekton-results-watcher` pod sometimes crashed and a `panic: runtime error: invalid memory address or nil pointer dereference` message was logged. With this update, the `tekton-results-watcher` pod does not crash.
+
+* Before this update, when using {tekton-results}, if you enabled authentication in {tekton-results}, you could not view information from {tekton-results} in the web console, because the web console failed to pass an authentication token to the {tekton-results} API. With this update, you can view information from {tekton-results} in the web console when authentication is enabled.
+
+* Before this update, when viewing information from {tekton-results} in the web console, if you scrolled down to the end of a page, the console failed to fetch the next set of records and some of the information was not displayed. With this update, if you scroll to the end of the page, records from {tekton-results} load correctly and all information displays correctly in the web console.