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.