CF Deployment Concourse Task Release

Brief

The goal of this guide is help you create a new CF-D Concourse Task public release. Please free to suggest changes based on your experience with the guide.

CF-Deployment Concourse Task (also cf-decota)

cf-decota contains set of concourse tasks for component teams to stitch together a CF pipeline for their product pipelines. Using cf-decota, teams can validate their changes with different CF-D environments. For e.g. a component team can test their new changes against master branch of CF-D to get quick feedback on their changes against a stable foundation.

Release Process

cf-decota is maintained by Release Integration team and the release is entirely up to RelInt's discretion. Each release can contain two types of changes:

1. Docker images are automatically updated by the concourse job whenever a team publishes a new release of their binary.
2. Updates made to concourse tasks (new tasks, updates or removal of tasks).

Overview

After completing these steps, you will have the following:

1. A published release note with version #
2. Master tagged with release version #

👉 Please ensure you have full access to ``cf-decota` repository. If not, please check with the team anchor.

Cut a new release of cf-decota.

💡 We usually increment the minor version if there are no breaking changes. If there are breaking changes, then increment the major version. If any of the concourse tasks that are breaking, as in it will require users of concourse tasks to re-configure their existing CI pipelines, then cf-decota you will release a major version.

1. Choose the right version
   1. For a minor version, navigate to the minor release concourse job.
   2. For a major version, navigate to the major release concourse job.
2. Click on the ➕ sign, which will kick off a new build. Once completed, the job will create a new tag version (using the previous version as a base - e.g. for minor v1.3.0 => v1.4.0, for major v1.3.0 => v2.0.0).
3. Take a note of the printed tag version

The version printed does not have the letter v in front of e.g. it will print 1.3.0 but the actual tag created is v1.3.0. The reason this is important is because github treats 1.3.0 and v1.3.0 as different tags.

4. Navigate to cf-decota releases section and click "Edit" on the previous draft version.
5. Look for the version created in step 3 and update the release notes with the changes included in this release.
6. Finally, click on Publish Release button.

Resources used in this guide

• CF Tracker
• cf-decota Repo
• cf-decota concourse
• Semantic Version