-
Notifications
You must be signed in to change notification settings - Fork 309
CF Deployment Concourse Task Release
The goal of this guide is help you create a new CF-D Concourse Task public release. Please free to make changes based on your experience with the guide.
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.
cf-decota is maintained by the same folks who maintain cf-deployment and the release is entirely up to their discretion. Releases tend to contain these two types of changes:
- Docker images are automatically updated by the concourse job whenever a team publishes a new release of their binary.
- Updates made to concourse tasks (new tasks, updates or removal of tasks).
After completing these steps, you will have the following:
- A published set of release notes
- A main branch tagged with the release version
💡 Increment the major version if there are any breaking changes. Otherwise, increment the minor version. If any of the concourse tasks have breaking changes, as in it will require users of concourse tasks to re-configure their existing CI pipelines, then make this a major release.
- Choose the type of semver bump
- For a minor version, navigate to the minor release concourse job.
- For a major version, navigate to the major release concourse job.
- Trigger a new build, which can take 5+ minutes. (Now is a good time to start compiling release notes.) Once completed, the job will create a new version tag.
- Navigate to
cf-decotareleases section and click "Edit" on the Draft release. - Browse the relevant set of commits and update the release notes appropriately.
- Finally, click on Publish Release button.