v0.15.0

This release:

• simplifies the installation and update procedure
• uses the pipeline run name as the Bitbucket build status key

For more details, please see the changelog.

To update your ODS pipeline installation, refer to the update instructions.

ods-pipeline-0.15.0

ODS Pipeline Helm chart 0.15.0

v0.14.0

This release is a major update to ODS Pipeline. The biggest change is that all tasks except the start and finish task have been moved out to their own repositories. This means that those tasks have their own lifecycle now, and the ods-pipeline repository just contains the plumbing part. It is now recommended to use remote resolution to reference tasks from your pipeline.

Apart from this change, there are three other big updates:

• All tekton resources have moved from v1beta1 to v1. This change should mostly be invisible to you.
• The installation and update procedure has been simplified a lot, removing the need to work with git subtree.
• The build skipping mechanism has been revised to work with natural repository layouts, not requiring the existence of an "output directory". This change affects the task that have been extracted into their own repositories.

For more details, please see the changelog.

To update your ODS pipeline installation, refer to the update instructions. As mentioned above the update procedure differs a lot compared to previous versions. In particular, you'll only need to retain the values.yaml file for future updates, and the file itself has changed quite a bit. There are no tasks and setup sub charts anymore. Delete the tasks section and un-indent the setup section, removing any field that is not present anymore in values.yaml.tmpl.

ods-pipeline-0.14.0

ODS Pipeline Helm chart 0.14.0

ods-pipeline-0.14.0-preview.1

ODS Pipeline Helm chart 0.14.0-preview.1

v0.13.2

This release fixes an issue with the artifact promotion, see #715.

For more details, please see the changelog.

To update your ODS pipeline installation, refer to the update instructions. There have been no changes to the values.yaml file compared to version 0.13.1.

v0.13.1

This release fixes several issues in the Gradle build task, as well as the SonarQube quality gate check for branches / pull requests.

For more details, please see the changelog.

To update your ODS pipeline installation, refer to the update instructions. There have been no changes to the values.yaml file compared to version 0.13.0.

v0.13.0

The highlight of this release is the new diff-only parameter of the ods-deploy-helm task. It allows to perform a diff without attempting an upgrade afterwards. Using this parameter it is possible to preview/verify changes to an Helm chart in a pull request without actually deploying the changes.

Apart from this, 0.13.0 contain an important bugfix for a regression introduced in 0.12.0, as well as two changes which are backwards-incompatible:

• Images are only pushed to the release namespace when Helm detects drift. The different behaviour avoids unnecessary image copying and should otherwise not be noticeable at all.
• Git clones are performed non-shallow by default now. This fixes complaints from SonarQube about missing Git blame information. As a drawback, clones may be noticeably slower than before. If you do not use SonarQube in your pipeline, you may revert to the previous behaviour by setting the start.clone-depth parameter to '1'.

For all changes and more details, please see the changelog.

To update your ODS pipeline installation, refer to the update instructions. There have been no changes to the values.yaml file compared to version 0.12.0.

v0.12.0

The highlights of this release are:

• Trigger-based params. With this change it is possible to set pipeline and task parameters based on selected triggers. The new concept provides a lot of flexibility and removes the need for the branchToEnvironment and environments configuration fields.
• Checkout of Git tags. Previously only branches could be checked out, now tags are supported both in response to webhook events as well as for subrepositories.
• More flexible artifact storage: pipelines can now specify (through trigger-based params) where to pull artifacts from and where to push them to, which allows for better environment protection through artefact repository configuration.

CAUTION! There have been numerous, backwards-incompatible changes to the configuration in ods.yaml. You will need to adjust your ods.yaml file for 0.12 to work. Please read through ODS configuration and Example project to understand the new approach. A brief overview of changes:

• pipeline was renamed to pipelines and only supports a list of pipelines now
• Within a trigger, the field event was renamed to events
• branchToEnvironment and environments was removed. The related values must be passed to the ods-deploy-helm task directly now. Typically, this would mean passing the namespace parameter to the task, likely through the use of trigger-based params.
• The params artifact-source and artifact-target have to be configured (through trigger-based params) for start and finish tasks (respectively) in order to preserve artifacts.
• Setting a version is no longer supported

Also, since there is no "environment" anymore, the chart's values/secrets files must be named according to the namespace now in order to be picked up.

For all changes and more details, please see the changelog.

To update your ODS pipeline installation, refer to the update instructions. There have been no changes to the values.yaml file compared to version 0.11.1.

v0.11.1

This release fixes an issue during Git checkout when the target Bitbucket server has basic auth disabled.

For more details, please see the changelog.

To update your ODS pipeline installation, refer to the update instructions. There have been no changes to the values.yaml file compared to version 0.11.0.