diff --git a/CHANGELOG.md b/CHANGELOG.md index 42450370..521fca91 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,6 +10,9 @@ listed in the changelog. ## [Unreleased] + +## [0.10.0] - 2023-02-27 + ### Added - Rendered task versions are available under `tasks/` now. These can be referenced directly from pipeline runs through [remote resolution](https://tekton.dev/docs/pipelines/pipelines/#specifying-remote-tasks). In future versions, tasks may be removed from the Helm chart and only be accessible via Git. See [#665](https://github.com/opendevstack/ods-pipeline/issues/665). diff --git a/README.md b/README.md index 4986f24d..f5162c90 100644 --- a/README.md +++ b/README.md @@ -52,10 +52,9 @@ For OpenShift Pipelines releases and its relationship to Tekton and OpenShift ve | ods-pipeline | OpenShift Pipelines | ODS Core/Quickstarters | |---|---|---| -| latest | 1.9 | 4.x | +| [0.10](https://github.com/opendevstack/ods-pipeline/releases/tag/v0.10.0) | 1.9 | 4.x | | [0.9](https://github.com/opendevstack/ods-pipeline/releases/tag/v0.9.0) | 1.6 | 4.x | | [0.8](https://github.com/opendevstack/ods-pipeline/releases/tag/v0.8.0) | 1.6 | 4.x | -| [0.7](https://github.com/opendevstack/ods-pipeline/releases/tag/v0.7.0) | 1.6 | 4.x | ## Contributing diff --git a/deploy/ods-pipeline/Chart.yaml b/deploy/ods-pipeline/Chart.yaml index ed993ee3..ebd37bfd 100644 --- a/deploy/ods-pipeline/Chart.yaml +++ b/deploy/ods-pipeline/Chart.yaml @@ -15,18 +15,18 @@ type: application # This is the chart version. This version number should be incremented each time you make changes # to the chart and its templates, including the app version. # Versions are expected to follow Semantic Versioning (https://semver.org/) -version: 0.9.0 +version: 0.10.0 # This is the version number of the application being deployed. This version number should be # incremented each time you make changes to the application. Versions are not expected to # follow Semantic Versioning. They should reflect the version the application is using. # It is recommended to use it with quotes. -appVersion: "0.9.0" +appVersion: "0.10.0" dependencies: - name: setup - version: 0.9.0 + version: 0.10.0 condition: setup.enabled - name: tasks - version: 0.9.0 + version: 0.10.0 condition: tasks.enabled diff --git a/deploy/ods-pipeline/charts/setup/Chart.yaml b/deploy/ods-pipeline/charts/setup/Chart.yaml index cfd58ee9..c6b65642 100644 --- a/deploy/ods-pipeline/charts/setup/Chart.yaml +++ b/deploy/ods-pipeline/charts/setup/Chart.yaml @@ -15,9 +15,9 @@ type: application # This is the chart version. This version number should be incremented each time you make changes # to the chart and its templates, including the app version. # Versions are expected to follow Semantic Versioning (https://semver.org/) -version: 0.9.0 +version: 0.10.0 # This is the version number of the application being deployed. This version number should be # incremented each time you make changes to the application. Versions are not expected to # follow Semantic Versioning. They should reflect the version the application is using. -appVersion: "0.9.0" +appVersion: "0.10.0" diff --git a/deploy/ods-pipeline/charts/tasks/Chart.yaml b/deploy/ods-pipeline/charts/tasks/Chart.yaml index 63c01531..275d1c35 100644 --- a/deploy/ods-pipeline/charts/tasks/Chart.yaml +++ b/deploy/ods-pipeline/charts/tasks/Chart.yaml @@ -15,9 +15,9 @@ type: application # This is the chart version. This version number should be incremented each time you make changes # to the chart and its templates, including the app version. # Versions are expected to follow Semantic Versioning (https://semver.org/) -version: 0.9.0 +version: 0.10.0 # This is the version number of the application being deployed. This version number should be # incremented each time you make changes to the application. Versions are not expected to # follow Semantic Versioning. They should reflect the version the application is using. -appVersion: "0.9.0" +appVersion: "0.10.0" diff --git a/docs/add-to-repository.adoc b/docs/add-to-repository.adoc index faa717d8..51e7207c 100644 --- a/docs/add-to-repository.adoc +++ b/docs/add-to-repository.adoc @@ -23,17 +23,17 @@ pipeline: - name: build taskRef: kind: Task - name: ods-build-go-v0-9-0 + name: ods-build-go-v0-10-0 workspaces: - name: source workspace: shared-workspace ---- -`ods-build-go-v0-9-0` runs tests and produces a Go binary. If you use another technology, e.g. a Java project using Gradle, exchange the task with `ods-build-gradle-v0-9-0`. See the link:tasks/[tasks reference] for available tasks. +`ods-build-go-v0-10-0` runs tests and produces a Go binary. If you use another technology, e.g. a Java project using Gradle, exchange the task with `ods-build-gradle-v0-10-0`. See the link:tasks/[tasks reference] for available tasks. === (Optionally) Create `Dockerfile` -If you want to create a container image with the produced Go binary, you can add the `ods-package-image-v0-9-0` task to the `tasks` list, like this: +If you want to create a container image with the produced Go binary, you can add the `ods-package-image-v0-10-0` task to the `tasks` list, like this: .ods.yaml [source,yaml] @@ -43,14 +43,14 @@ pipeline: - name: build taskRef: kind: Task - name: ods-build-go-v0-9-0 + name: ods-build-go-v0-10-0 workspaces: - name: source workspace: shared-workspace - name: package taskRef: kind: Task - name: ods-package-image-v0-9-0 + name: ods-package-image-v0-10-0 runAfter: - build workspaces: @@ -72,13 +72,13 @@ EXPOSE 8080 CMD ["./app"] ---- -NOTE: `ods-build-go-v0-9-0` produces a binary called `app` and places it at `docker/app` so that it can be referenced in the `Dockerfile` and copied into the image by the `ods-package-image-v0-9-0` task. +NOTE: `ods-build-go-v0-10-0` produces a binary called `app` and places it at `docker/app` so that it can be referenced in the `Dockerfile` and copied into the image by the `ods-package-image-v0-10-0` task. NOTE: Pay attention to the `runAfter` configuration in the task list: it ensures that the tasks run sequentially and can use the outputs from the previous task(s). === (Optionally) Create Helm Chart -If you want to deploy the created image, you can add the `ods-deploy-helm-v0-9-0` task to the `tasks` list and configure which branches should be deployed to which Kubernetes namespaces, like this: +If you want to deploy the created image, you can add the `ods-deploy-helm-v0-10-0` task to the `tasks` list and configure which branches should be deployed to which Kubernetes namespaces, like this: .ods.yaml [source,yaml] @@ -97,14 +97,14 @@ pipeline: - name: build taskRef: kind: Task - name: ods-build-go-v0-9-0 + name: ods-build-go-v0-10-0 workspaces: - name: source workspace: shared-workspace - name: package taskRef: kind: Task - name: ods-package-image-v0-9-0 + name: ods-package-image-v0-10-0 runAfter: - build workspaces: @@ -113,7 +113,7 @@ pipeline: - name: deploy taskRef: kind: Task - name: ods-deploy-helm-v0-9-0 + name: ods-deploy-helm-v0-10-0 runAfter: - package workspaces: diff --git a/docs/convert-quickstarter-component.adoc b/docs/convert-quickstarter-component.adoc index 2cacdfa1..e0191288 100644 --- a/docs/convert-quickstarter-component.adoc +++ b/docs/convert-quickstarter-component.adoc @@ -101,14 +101,14 @@ pipeline: - name: backend-build-go taskRef: kind: Task - name: ods-build-go-v0-9-0 + name: ods-build-go-v0-10-0 workspaces: - name: source workspace: shared-workspace - name: backend-package-image taskRef: kind: Task - name: ods-package-image-v0-9-0 + name: ods-package-image-v0-10-0 runAfter: - backend-build-go workspaces: @@ -117,7 +117,7 @@ pipeline: - name: backend-deploy taskRef: kind: Task - name: ods-deploy-helm-v0-9-0 + name: ods-deploy-helm-v0-10-0 runAfter: - backend-package-image workspaces: @@ -125,13 +125,13 @@ pipeline: workspace: shared-workspace ---- -What has been done in Jenkins in `stageCheckFormat`, `stageLint`, `stageUnitTest`, `stageBuild` and `odsComponentStageScanWithSonar` is now done by the `ods-build-go-v0-9-0` task. If you have modified how the application is tested and built, or added further steps, you will need to create your own Tekton tasks reflecting those changes. See the link:authoring-tasks.adoc[authoring tasks] guide. +What has been done in Jenkins in `stageCheckFormat`, `stageLint`, `stageUnitTest`, `stageBuild` and `odsComponentStageScanWithSonar` is now done by the `ods-build-go-v0-10-0` task. If you have modified how the application is tested and built, or added further steps, you will need to create your own Tekton tasks reflecting those changes. See the link:authoring-tasks.adoc[authoring tasks] guide. -Building the container image is now done in `ods-package-image-v0-9-0` instead of in `odsComponentStageBuildOpenShiftImage`. The task continues to use the existing `docker/Dockerfile` file, which does not need to change much if at all. Consult the task reference in question for more information. In the case of Go, the link:tasks/ods-build-go.adoc[`ods-build-go` task reference] states that the resulting Go binary is named `app` and placed into the `docker` directory. Make sure that your `docker/Dockerfile` copies `app`, not e.g. `app_linux_amd64` (as is the default for an ODS 4.x based Go quickstarter). +Building the container image is now done in `ods-package-image-v0-10-0` instead of in `odsComponentStageBuildOpenShiftImage`. The task continues to use the existing `docker/Dockerfile` file, which does not need to change much if at all. Consult the task reference in question for more information. In the case of Go, the link:tasks/ods-build-go.adoc[`ods-build-go` task reference] states that the resulting Go binary is named `app` and placed into the `docker` directory. Make sure that your `docker/Dockerfile` copies `app`, not e.g. `app_linux_amd64` (as is the default for an ODS 4.x based Go quickstarter). == Create Helm Chart -Finally, the application is deployed in `ods-deploy-helm-v0-9-0` as opposed to `odsComponentStageRolloutOpenShiftDeployment`. +Finally, the application is deployed in `ods-deploy-helm-v0-10-0` as opposed to `odsComponentStageRolloutOpenShiftDeployment`. Let's look at this deployment piece in detail. The new Tekton task makes use of Helm to define and deploy the Kubernetes resources to use. Your existing repository might not define Kubernetes resources at all (this is the default), or they might be expressed as OpenShift templates (in a folder named `openshift`) and applied with link:https://github.com/opendevstack/tailor[Tailor]. ODS pipeline only supports Helm at the moment, and requires the Kubernetes resources (the Helm "chart") to be under version control. It is recommended to start with the link:https://github.com/opendevstack/ods-pipeline/tree/sample-helm-chart[sample chart provided in this repository]. If the existing component controlled resources via Tailor, please see the link:https://github.com/opendevstack/tailor/wiki/Migrating-from-Tailor-to-Helm#ods-quickstarter-migration[ODS Quickstarter Migration Guide] of Tailor as well. == Configure Webhook diff --git a/docs/example-project.adoc b/docs/example-project.adoc index 063e2134..00df89fb 100644 --- a/docs/example-project.adoc +++ b/docs/example-project.adoc @@ -33,14 +33,14 @@ pipeline: - name: build taskRef: kind: Task - name: ods-build-go-v0-9-0 + name: ods-build-go-v0-10-0 workspaces: - name: source workspace: shared-workspace - name: package taskRef: kind: Task - name: ods-package-image-v0-9-0 + name: ods-package-image-v0-10-0 runAfter: - build workspaces: @@ -49,7 +49,7 @@ pipeline: - name: deploy taskRef: kind: Task - name: ods-deploy-helm-v0-9-0 + name: ods-deploy-helm-v0-10-0 runAfter: - package workspaces: @@ -74,14 +74,14 @@ pipeline: - name: build taskRef: kind: Task - name: ods-build-npm-v0-9-0 + name: ods-build-npm-v0-10-0 workspaces: - name: source workspace: shared-workspace - name: package taskRef: kind: Task - name: ods-package-image-v0-9-0 + name: ods-package-image-v0-10-0 runAfter: - build workspaces: @@ -90,7 +90,7 @@ pipeline: - name: deploy taskRef: kind: Task - name: ods-deploy-helm-v0-9-0 + name: ods-deploy-helm-v0-10-0 runAfter: - package workspaces: @@ -134,7 +134,7 @@ pipeline: - name: deploy taskRef: kind: Task - name: ods-deploy-helm-v0-9-0 + name: ods-deploy-helm-v0-10-0 workspaces: - name: source workspace: shared-workspace diff --git a/docs/installation.adoc b/docs/installation.adoc index c18ac987..10c58d7e 100644 --- a/docs/installation.adoc +++ b/docs/installation.adoc @@ -33,7 +33,7 @@ Now use `git subtree` to get the required source files. The following commands m [source] ---- -pipelineGitRef=v0.9.0 # Pick the version you want to install +pipelineGitRef=v0.10.0 # Pick the version you want to install git fetch --depth=1 https://github.com/opendevstack/ods-pipeline.git $pipelineGitRef:ods-pipeline-$pipelineGitRef && \ git checkout ods-pipeline-$pipelineGitRef && \ @@ -101,7 +101,7 @@ You may fetch updates (e.g. new versions) of `ods-pipeline` like this: [source] ---- -pipelineGitRef=v0.9.0 # Pick the version you want to update to +pipelineGitRef=v0.10.0 # Pick the version you want to update to git br -D ods-pipeline-$pipelineGitRef subtree-split-branch-$pipelineGitRef || true && \ git fetch --depth=1 https://github.com/opendevstack/ods-pipeline.git $pipelineGitRef:ods-pipeline-$pipelineGitRef && \ @@ -145,4 +145,4 @@ TIP: The credentials stored in the K8s secrets will not be updated. If you need ==== Finishing the update -Once the resources in your namespace are updated, you likely have to update the `ods.yaml` files in your repository to point to the new tasks, e.g. changing `ods-build-go-v0-8-0` to `ods-build-go-v0-9-0`. Whether or not you have to update the `ods.yaml` file depends whether the task suffix (controlled by the value `taskSuffix`) has changed due to the update. +Once the resources in your namespace are updated, you likely have to update the `ods.yaml` files in your repository to point to the new tasks, e.g. changing `ods-build-go-v0-9-0` to `ods-build-go-v0-10-0`. Whether or not you have to update the `ods.yaml` file depends whether the task suffix (controlled by the value `taskSuffix`) has changed due to the update. diff --git a/docs/introduction.adoc b/docs/introduction.adoc index 0e7e45ee..fab7f40f 100644 --- a/docs/introduction.adoc +++ b/docs/introduction.adoc @@ -72,14 +72,14 @@ pipeline: - name: build-go taskRef: kind: Task - name: ods-build-go-v0-9-0 + name: ods-build-go-v0-10-0 workspaces: - name: source workspace: shared-workspace - name: package-image taskRef: kind: Task - name: ods-package-image-v0-9-0 + name: ods-package-image-v0-10-0 runAfter: - build-go workspaces: @@ -88,7 +88,7 @@ pipeline: - name: deploy-helm taskRef: kind: Task - name: ods-deploy-helm-v0-9-0 + name: ods-deploy-helm-v0-10-0 runAfter: - package-image workspaces: diff --git a/docs/ods-configuration.adoc b/docs/ods-configuration.adoc index 384eae2e..a0877a4b 100644 --- a/docs/ods-configuration.adoc +++ b/docs/ods-configuration.adoc @@ -27,14 +27,14 @@ pipeline: - name: build taskRef: kind: Task - name: ods-build-go-v0-9-0 + name: ods-build-go-v0-10-0 workspaces: - name: source workspace: shared-workspace - name: package taskRef: kind: Task - name: ods-package-image-v0-9-0 + name: ods-package-image-v0-10-0 runAfter: - build workspaces: diff --git a/docs/releasing.adoc b/docs/releasing.adoc index ff579fc8..0ca71552 100644 --- a/docs/releasing.adoc +++ b/docs/releasing.adoc @@ -13,7 +13,7 @@ ODS pipeline follows https://semver.org[Semantic Versioning 2.0.0]. This means b Ensure that all issues with the milestone of the release are resolved (or re-assign the issues to a future release). Further, run `govulncheck ./...` locally to check if there are any vulnerabilities that need to be fixed before the release. For more information on `govulncheck`, see https://go.dev/blog/vuln. === Preparing the release -The current version is hardcoded in a few places across the repository. All of these places must be updated for a release (search for `X.Y.Z` and `X-Y-Z`, ignoring the `test` directory). See the https://github.com/opendevstack/ods-pipeline/commit/49e0934fcd35b35439a4adb993fb2adbcb0d7107[commit releasing 0.5.0] as a reference. Commit the changes and push to the `master` branch. +The current version is hardcoded in a few places across the repository. All of these places must be updated for a release (search for `X.Y.Z` and `X-Y-Z`, ignoring the `test` and `tasks` directory). After the version numbers have been updated, run `make tasks` to update the rendered tasks, then mark the new version as released in the changelog and update the readme file. Commit the changes and push to the `master` branch. === Publishing the release Draft a new GitHub release, creating a new tag in the process (e.g. `v0.2.0`). The description should be like this: diff --git a/tasks/ods-build-go.yaml b/tasks/ods-build-go.yaml index a0d8de9c..b9d6327a 100644 --- a/tasks/ods-build-go.yaml +++ b/tasks/ods-build-go.yaml @@ -10,7 +10,7 @@ spec: description: | Builds Go (module) applications. - See https://github.com/opendevstack/ods-pipeline/blob/v0.9.0/docs/tasks/ods-build-go.adoc + See https://github.com/opendevstack/ods-pipeline/blob/v0.10.0/docs/tasks/ods-build-go.adoc params: - name: working-dir description: | @@ -70,7 +70,7 @@ spec: steps: - name: build-go-binary # Image is built from build/package/Dockerfile.go-toolset. - image: 'ghcr.io/opendevstack/ods-pipeline/ods-go-toolset:0.9.0' + image: 'ghcr.io/opendevstack/ods-pipeline/ods-go-toolset:0.10.0' env: - name: HOME value: '/tekton/home' @@ -128,7 +128,7 @@ spec: workingDir: $(workspaces.source.path) - name: scan-with-sonar # Image is built from build/package/Dockerfile.sonar. - image: 'ghcr.io/opendevstack/ods-pipeline/ods-sonar:0.9.0' + image: 'ghcr.io/opendevstack/ods-pipeline/ods-sonar:0.10.0' env: - name: HOME value: '/tekton/home' diff --git a/tasks/ods-build-gradle.yaml b/tasks/ods-build-gradle.yaml index a9a55559..68e00abe 100644 --- a/tasks/ods-build-gradle.yaml +++ b/tasks/ods-build-gradle.yaml @@ -10,7 +10,7 @@ spec: description: | Builds Gradle applications. - See https://github.com/opendevstack/ods-pipeline/blob/v0.9.0/docs/tasks/ods-build-gradle.adoc + See https://github.com/opendevstack/ods-pipeline/blob/v0.10.0/docs/tasks/ods-build-gradle.adoc params: - name: working-dir description: | @@ -74,7 +74,7 @@ spec: steps: - name: build-gradle-binary # Image is built from build/package/Dockerfile.gradle-toolset. - image: 'ghcr.io/opendevstack/ods-pipeline/ods-gradle-toolset:0.9.0' + image: 'ghcr.io/opendevstack/ods-pipeline/ods-gradle-toolset:0.10.0' env: - name: DEBUG valueFrom: @@ -146,7 +146,7 @@ spec: workingDir: $(workspaces.source.path) - name: scan-with-sonar # Image is built from build/package/Dockerfile.sonar. - image: 'ghcr.io/opendevstack/ods-pipeline/ods-sonar:0.9.0' + image: 'ghcr.io/opendevstack/ods-pipeline/ods-sonar:0.10.0' env: - name: HOME value: '/tekton/home' diff --git a/tasks/ods-build-npm.yaml b/tasks/ods-build-npm.yaml index 65901eaf..9b986770 100644 --- a/tasks/ods-build-npm.yaml +++ b/tasks/ods-build-npm.yaml @@ -10,7 +10,7 @@ spec: description: | Builds Node.js applications using npm. - See https://github.com/opendevstack/ods-pipeline/blob/v0.9.0/docs/tasks/ods-build-npm.adoc + See https://github.com/opendevstack/ods-pipeline/blob/v0.10.0/docs/tasks/ods-build-npm.adoc params: - name: working-dir description: | @@ -74,7 +74,7 @@ spec: steps: - name: build-npm # Image is built from build/package/Dockerfile.node-npm-toolset. - image: 'ghcr.io/opendevstack/ods-pipeline/ods-node$(params.node-version)-npm-toolset:0.9.0' + image: 'ghcr.io/opendevstack/ods-pipeline/ods-node$(params.node-version)-npm-toolset:0.10.0' env: - name: HOME value: '/tekton/home' @@ -145,7 +145,7 @@ spec: workingDir: $(workspaces.source.path) - name: scan-with-sonar # Image is built from build/package/Dockerfile.sonar. - image: 'ghcr.io/opendevstack/ods-pipeline/ods-sonar:0.9.0' + image: 'ghcr.io/opendevstack/ods-pipeline/ods-sonar:0.10.0' env: - name: HOME value: '/tekton/home' diff --git a/tasks/ods-build-python.yaml b/tasks/ods-build-python.yaml index 07fdf9bf..f8ba388d 100644 --- a/tasks/ods-build-python.yaml +++ b/tasks/ods-build-python.yaml @@ -10,7 +10,7 @@ spec: description: | Builds Python applications. - See https://github.com/opendevstack/ods-pipeline/blob/v0.9.0/docs/tasks/ods-build-python.adoc + See https://github.com/opendevstack/ods-pipeline/blob/v0.10.0/docs/tasks/ods-build-python.adoc params: - name: working-dir description: | @@ -62,7 +62,7 @@ spec: steps: - name: build-python # Image is built from build/package/Dockerfile.python-toolset. - image: 'ghcr.io/opendevstack/ods-pipeline/ods-python-toolset:0.9.0' + image: 'ghcr.io/opendevstack/ods-pipeline/ods-python-toolset:0.10.0' env: - name: HOME value: '/tekton/home' @@ -133,7 +133,7 @@ spec: workingDir: $(workspaces.source.path) - name: scan-with-sonar # Image is built from build/package/Dockerfile.sonar. - image: 'ghcr.io/opendevstack/ods-pipeline/ods-sonar:0.9.0' + image: 'ghcr.io/opendevstack/ods-pipeline/ods-sonar:0.10.0' env: - name: HOME value: '/tekton/home' diff --git a/tasks/ods-deploy-helm.yaml b/tasks/ods-deploy-helm.yaml index c768deb1..23b8f282 100644 --- a/tasks/ods-deploy-helm.yaml +++ b/tasks/ods-deploy-helm.yaml @@ -10,7 +10,7 @@ spec: description: | Deploy Helm charts. - See https://github.com/opendevstack/ods-pipeline/blob/v0.9.0/docs/tasks/ods-deploy-helm.adoc + See https://github.com/opendevstack/ods-pipeline/blob/v0.10.0/docs/tasks/ods-deploy-helm.adoc params: - name: chart-dir description: Helm chart directory that will be deployed @@ -46,7 +46,7 @@ spec: steps: - name: helm-upgrade-from-repo # Image is built from build/package/Dockerfile.helm. - image: 'ghcr.io/opendevstack/ods-pipeline/ods-helm:0.9.0' + image: 'ghcr.io/opendevstack/ods-pipeline/ods-helm:0.10.0' env: - name: DEBUG valueFrom: diff --git a/tasks/ods-finish.yaml b/tasks/ods-finish.yaml index 5c044f69..4cc0ef35 100644 --- a/tasks/ods-finish.yaml +++ b/tasks/ods-finish.yaml @@ -10,7 +10,7 @@ spec: description: | Finishes the pipeline run. - See https://github.com/opendevstack/ods-pipeline/blob/v0.9.0/docs/tasks/ods-finish.adoc + See https://github.com/opendevstack/ods-pipeline/blob/v0.10.0/docs/tasks/ods-finish.adoc params: - name: pipeline-run-name description: Name of pipeline run. @@ -21,7 +21,7 @@ spec: steps: - name: ods-finish # Image is built from build/package/Dockerfile.finish. - image: 'ghcr.io/opendevstack/ods-pipeline/ods-finish:0.9.0' + image: 'ghcr.io/opendevstack/ods-pipeline/ods-finish:0.10.0' env: - name: HOME value: '/tekton/home' diff --git a/tasks/ods-package-image.yaml b/tasks/ods-package-image.yaml index df8cf9bd..59e3cbcb 100644 --- a/tasks/ods-package-image.yaml +++ b/tasks/ods-package-image.yaml @@ -10,7 +10,7 @@ spec: description: | Packages applications into container images using buildah. - See https://github.com/opendevstack/ods-pipeline/blob/v0.9.0/docs/tasks/ods-package-image.adoc + See https://github.com/opendevstack/ods-pipeline/blob/v0.10.0/docs/tasks/ods-package-image.adoc params: - name: registry description: Image registry to push image to. @@ -62,7 +62,7 @@ spec: steps: - name: package-image # Image is built from build/package/Dockerfile.package-image. - image: 'ghcr.io/opendevstack/ods-pipeline/ods-package-image:0.9.0' + image: 'ghcr.io/opendevstack/ods-pipeline/ods-package-image:0.10.0' env: - name: NEXUS_URL valueFrom: @@ -113,7 +113,7 @@ spec: workingDir: $(workspaces.source.path) - name: aqua-scan # Image is built from build/package/Dockerfile.aqua-scan. - image: 'ghcr.io/opendevstack/ods-pipeline/ods-aqua-scan:0.9.0' + image: 'ghcr.io/opendevstack/ods-pipeline/ods-aqua-scan:0.10.0' env: - name: HOME value: '/tekton/home' diff --git a/tasks/ods-start.yaml b/tasks/ods-start.yaml index f0b965cd..af22e3f3 100644 --- a/tasks/ods-start.yaml +++ b/tasks/ods-start.yaml @@ -10,7 +10,7 @@ spec: description: | Starts the pipeline run. - See https://github.com/opendevstack/ods-pipeline/blob/v0.9.0/docs/tasks/ods-start.adoc + See https://github.com/opendevstack/ods-pipeline/blob/v0.10.0/docs/tasks/ods-start.adoc params: - name: url description: Git URL to clone @@ -94,7 +94,7 @@ spec: steps: - name: ods-start # Image is built from build/package/Dockerfile.start. - image: 'ghcr.io/opendevstack/ods-pipeline/ods-start:0.9.0' + image: 'ghcr.io/opendevstack/ods-pipeline/ods-start:0.10.0' env: - name: HOME value: '/tekton/home'