|
| 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-9_{context}"] |
| 6 | += Release notes for {pipelines-title} General Availability 1.9 |
| 7 | + |
| 8 | +With this update, {pipelines-title} General Availability (GA) 1.9 is available on {product-title} 4.11 and later versions. |
| 9 | + |
| 10 | +[id="new-features-1-9_{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.9. |
| 14 | + |
| 15 | +[id="pipelines-new-features-1-9_{context}"] |
| 16 | +=== Pipelines |
| 17 | + |
| 18 | +* With this update, you can specify pipeline parameters and results in arrays and object dictionary forms. |
| 19 | + |
| 20 | +* This update provides support for Container Storage Interface (CSI) and projected volumes for your workspace. |
| 21 | + |
| 22 | +* With this update, you can specify the `stdoutConfig` and `stderrConfig` parameters when defining pipeline steps. Defining these parameters helps to capture standard output and standard error, associated with steps, to local files. |
| 23 | + |
| 24 | +* With this update, you can add variables in the `steps[].onError` event handler, for example, `$(params.CONTINUE)`. |
| 25 | + |
| 26 | +* With this update, you can use the output from the `finally` task in the `PipelineResults` definition. For example, `$(finally.<pipelinetask-name>.result.<result-name>)`, where `<pipelinetask-name>` denotes the pipeline task name and `<result-name>` denotes the result name. |
| 27 | + |
| 28 | +* This update supports task-level resource requirements for a task run. |
| 29 | + |
| 30 | +* With this update, you do not need to recreate parameters that are shared, based on their names, between a pipeline and the defined tasks. This update is part of a developer preview feature. |
| 31 | + |
| 32 | +* This update adds support for remote resolution, such as built-in git, cluster, bundle, and hub resolvers. |
| 33 | + |
| 34 | + |
| 35 | +[id="triggers-new-features-1-9_{context}"] |
| 36 | +=== Triggers |
| 37 | + |
| 38 | +* This update adds the `Interceptor` CRD to define `NamespacedInterceptor`. You can use `NamespacedInterceptor` in the `kind` section of interceptors reference in triggers or in the `EventListener` specification. |
| 39 | + |
| 40 | +* This update enables `CloudEvents`. |
| 41 | + |
| 42 | +* With this update, you can configure the webhook port number when defining a trigger. |
| 43 | + |
| 44 | +* This update supports using trigger `eventID` as input to `TriggerBinding`. |
| 45 | + |
| 46 | +* This update supports validation and rotation of certificates for the `ClusterInterceptor` server. |
| 47 | +** Triggers perform certificate validation for core interceptors and rotate a new certificate to `ClusterInterceptor` when its certificate expires. |
| 48 | + |
| 49 | + |
| 50 | +[id="cli-new-features-1-9_{context}"] |
| 51 | +=== CLI |
| 52 | + |
| 53 | +* This update supports showing annotations in the `describe` command. |
| 54 | + |
| 55 | +* This update supports showing pipeline, tasks, and timeout in the `pr describe` command. |
| 56 | + |
| 57 | +* This update adds flags to provide pipeline, tasks, and timeout in the `pipeline start` command. |
| 58 | + |
| 59 | +* This update supports showing the presence of workspace, optional or mandatory, in the `describe` command of a task and pipeline. |
| 60 | + |
| 61 | +* This update adds the `timestamps` flag to show logs with a timestamp. |
| 62 | + |
| 63 | +* This update adds a new flag `--ignore-running-pipelinerun`, which ignores the deletion of `TaskRun` associated with `PipelineRun`. |
| 64 | + |
| 65 | +* This update adds support for experimental commands. This update also adds experimental subcommands, `sign` and `verify` to the `tkn` CLI tool. |
| 66 | + |
| 67 | +* This update makes the Z shell (Zsh) completion feature usable without generating any files. |
| 68 | + |
| 69 | +* This update introduces a new CLI tool called `opc`. It is anticipated that an upcoming release will replace the `tkn` CLI tool with `opc`. |
| 70 | ++ |
| 71 | +[IMPORTANT] |
| 72 | +==== |
| 73 | +* The new CLI tool `opc` is a Technology Preview feature. |
| 74 | +* `opc` will be a replacement for `tkn` with additional {pipelines-title} specific features, which do not necessarily fit in `tkn`. |
| 75 | +==== |
| 76 | + |
| 77 | +[id="operator-new-features-1-9_{context}"] |
| 78 | +=== Operator |
| 79 | + |
| 80 | +* With this update, you can install {pac} as a separate component, not as a part of `TektonAddon`. You can configure {pac} in the `TektonConfig` CRD. |
| 81 | + |
| 82 | +* With this update, you can also modify {pac} configurations in the `TektonConfig` CRD. |
| 83 | + |
| 84 | +* With this update, if you disable the developer perspective, the Operator does not install developer console related custom resources. |
| 85 | + |
| 86 | +* This update includes `ClusterTriggerBinding` support for Bitbucket Server and Bitbucket Cloud and helps you to reuse a `TriggerBinding` across your entire cluster. |
| 87 | + |
| 88 | +[id="resolver-new-features-1-9_{context}"] |
| 89 | +=== Resolvers |
| 90 | + |
| 91 | +:FeatureName: Resolvers |
| 92 | +include::snippets/technology-preview.adoc[] |
| 93 | + |
| 94 | +* With this update, you can configure pipeline resolvers in the `TektonConfig` CRD. You can enable or disable these pipeline resolvers: `enable-bundles-resolver`, `enable-cluster-resolver`, `enable-git-resolver`, and `enable-hub-resolver`. |
| 95 | ++ |
| 96 | +[source,yaml,subs="attributes+"] |
| 97 | +---- |
| 98 | +apiVersion: operator.tekton.dev/v1alpha1 |
| 99 | +kind: TektonConfig |
| 100 | +metadata: |
| 101 | + name: config |
| 102 | +spec: |
| 103 | + pipeline: |
| 104 | + enable-bundles-resolver: true |
| 105 | + enable-cluster-resolver: true |
| 106 | + enable-git-resolver: true |
| 107 | + enable-hub-resolver: true |
| 108 | +... |
| 109 | +---- |
| 110 | ++ |
| 111 | +You can also provide resolver specific configurations in `TektonConfig`. For example, you can define the following fields in the `map[string]string` format to set configurations for individual resolvers: |
| 112 | ++ |
| 113 | +[source,yaml,subs="attributes+"] |
| 114 | +---- |
| 115 | +apiVersion: operator.tekton.dev/v1alpha1 |
| 116 | +kind: TektonConfig |
| 117 | +metadata: |
| 118 | + name: config |
| 119 | +spec: |
| 120 | + pipeline: |
| 121 | + bundles-resolver-config: |
| 122 | + default-service-account: pipelines |
| 123 | + cluster-resolver-config: |
| 124 | + default-namespace: test |
| 125 | + git-resolver-config: |
| 126 | + server-url: localhost.com |
| 127 | + hub-resolver-config: |
| 128 | + default-tekton-hub-catalog: tekton |
| 129 | +... |
| 130 | +---- |
| 131 | + |
| 132 | + |
| 133 | +[id="chains-new-features-1-9_{context}"] |
| 134 | +=== {tekton-chains} |
| 135 | + |
| 136 | +:FeatureName: Tekton Chains |
| 137 | +include::snippets/technology-preview.adoc[] |
| 138 | + |
| 139 | +* Before this update, only Open Container Initiative (OCI) images were supported as outputs of `TaskRun` in the in-toto provenance agent. This update adds in-toto provenance metadata as outputs with these suffixes, `ARTIFACT_URI` and `ARTIFACT_DIGEST`. |
| 140 | + |
| 141 | +* Before this update, only `TaskRun` attestations were supported. This update adds support for `PipelineRun` attestations as well. |
| 142 | + |
| 143 | +* This update adds support for {tekton-chains} to get the `imgPullSecret` parameter from the pod template. This update helps you to configure repository authentication based on each pipeline run or task run without modifying the service account. |
| 144 | + |
| 145 | +[id="tekton-hub-new-features-1-9_{context}"] |
| 146 | +=== {tekton-hub} |
| 147 | + |
| 148 | +:FeatureName: {tekton-hub} |
| 149 | +include::snippets/technology-preview.adoc[] |
| 150 | + |
| 151 | +* With this update, as an administrator, you can use an external database, such as Crunchy PostgreSQL with {tekton-hub}, instead of using the default {tekton-hub} database. This update helps you to perform the following actions: |
| 152 | +** Specify the coordinates of an external database to be used with {tekton-hub} |
| 153 | +** Disable the default {tekton-hub} database deployed by the Operator |
| 154 | + |
| 155 | +* This update removes the dependency of `config.yaml` from external Git repositories and moves the complete configuration data into the API `ConfigMap`. This update helps an administrator to perform the following actions: |
| 156 | +** Add the configuration data, such as categories, catalogs, scopes, and defaultScopes in the {tekton-hub} custom resource. |
| 157 | +** Modify {tekton-hub} configuration data on the cluster. All modifications are preserved upon Operator upgrades. |
| 158 | +** Update the list of catalogs for {tekton-hub} |
| 159 | +** Change the categories for {tekton-hub} |
| 160 | ++ |
| 161 | +[NOTE] |
| 162 | +==== |
| 163 | +If you do not add any configuration data, you can use the default data in the API `ConfigMap` for {tekton-hub} configurations. |
| 164 | +==== |
| 165 | + |
| 166 | +[id="pac-new-features-1-9_{context}"] |
| 167 | +=== {pac} |
| 168 | + |
| 169 | +* This update adds support for concurrency limit in the `Repository` CRD to define the maximum number of `PipelineRuns` running for a repository at a time. The `PipelineRuns` from a pull request or a push event are queued in alphabetical order. |
| 170 | + |
| 171 | +* This update adds a new command `tkn pac logs` for showing the logs of the latest pipeline run for a repository. |
| 172 | + |
| 173 | +* This update supports advanced event matching on file path for push and pull requests to GitHub and GitLab. For example, you can use the Common Expression Language (CEL) to run a pipeline only if a path has changed for any markdown file in the `docs` directory. |
| 174 | ++ |
| 175 | +[source,yaml] |
| 176 | +---- |
| 177 | + ... |
| 178 | + annotations: |
| 179 | + pipelinesascode.tekton.dev/on-cel-expression: | |
| 180 | + event == "pull_request" && "docs/*.md".pathChanged() |
| 181 | +---- |
| 182 | + |
| 183 | +* With this update, you can reference a remote pipeline in the `pipelineRef:` object using annotations. |
| 184 | + |
| 185 | +* With this update, you can auto-configure new GitHub repositories with {pac}, which sets up a namespace and creates a `Repository` CRD for your GitHub repository. |
| 186 | + |
| 187 | +* With this update, {pac} generates metrics for `PipelineRuns` with provider information. |
| 188 | + |
| 189 | +* This update provides the following enhancements for the `tkn-pac` plugin: |
| 190 | +** Detects running pipelines correctly |
| 191 | +** Fixes showing duration when there is no failure completion time |
| 192 | +** Shows an error snippet and highlights the error regular expression pattern in the `tkn-pac describe` command |
| 193 | +** Adds the `use-real-time` switch to the `tkn-pac ls` and `tkn-pac describe` commands |
| 194 | +** Imports the `tkn-pac` logs documentation |
| 195 | +** Shows `pipelineruntimeout` as a failure in the `tkn-pac ls` and `tkn-pac describe` commands. |
| 196 | +** Show a specific pipeline run failure with the `--target-pipelinerun` option. |
| 197 | + |
| 198 | +* With this update, you can view the errors for your pipeline run in the form of a version control system (VCS) comment or a small snippet in the GitHub checks. |
| 199 | + |
| 200 | +* With this update, {pac} optionally can detect errors inside the tasks if they are of a simple format and add those tasks as annotations in GitHub. This update is part of a developer preview feature. |
| 201 | + |
| 202 | +* This update adds the following new commands: |
| 203 | +** `tkn-pac webhook add`: Adds a webhook to project repository settings and updates the `webhook.secret` key in the existing `k8s Secret` object without updating the repository. |
| 204 | +** `tkn-pac webhook update-token`: Updates provider token for an existing `k8s Secret` object without updating the repository. |
| 205 | + |
| 206 | +* This update enhances functionality of the `tkn-pac create repo` command, which creates and configures webhooks for GitHub, GitLab, and BitbucketCloud along with creating repositories. |
| 207 | + |
| 208 | +* With this update, the `tkn-pac describe` command shows the latest fifty events in a sorted order. |
| 209 | + |
| 210 | +* This update adds the `--last` option to the `tkn-pac logs` command. |
| 211 | + |
| 212 | +* With this update, the `tkn-pac resolve` command prompts for a token on detecting a `git_auth_secret` in the file template. |
| 213 | + |
| 214 | +* With this update, {pac} hides secrets from log snippets to avoid exposing secrets in the GitHub interface. |
| 215 | + |
| 216 | +* With this update, the secrets automatically generated for `git_auth_secret` are an owner reference with `PipelineRun`. The secrets get cleaned with the `PipelineRun`, not after the pipeline run execution. |
| 217 | + |
| 218 | +* This update adds support to cancel a pipeline run with the `/cancel` comment. |
| 219 | + |
| 220 | +* Before this update, the GitHub apps token scoping was not defined and tokens would be used on every repository installation. With this update, you can scope the GitHub apps token to the target repository using the following parameters: |
| 221 | +** `secret-github-app-token-scoped`: Scopes the app token to the target repository, not to every repository the app installation has access to. |
| 222 | +** `secret-github-app-scope-extra-repos`: Customizes the scoping of the app token with an additional owner or repository. |
| 223 | + |
| 224 | +* With this update, you can use {pac} with your own Git repositories that are hosted on GitLab. |
| 225 | + |
| 226 | +* With this update, you can access pipeline execution details in the form of kubernetes events in your namespace. These details help you to troubleshoot pipeline errors without needing access to admin namespaces. |
| 227 | + |
| 228 | +* This update supports authentication of URLs in the {pac} resolver with the Git provider. |
| 229 | + |
| 230 | +* With this update, you can set the name of the hub catalog by using a setting in the `pipelines-as-code` config map. |
| 231 | + |
| 232 | +* With this update, you can set the maximum and default limits for the `max-keep-run` parameter. |
| 233 | + |
| 234 | +* This update adds documents on how to inject custom Secure Sockets Layer (SSL) certificates in {pac} to let you connect to provider instance with custom certificates. |
| 235 | + |
| 236 | +* With this update, the `PipelineRun` resource definition has the log URL included as an annotation. For example, the `tkn-pac describe` command shows the log link when describing a `PipelineRun`. |
| 237 | + |
| 238 | +* With this update, `tkn-pac` logs show repository name, instead of `PipelineRun` name. |
0 commit comments