Temporary Major Stemcell Bump Release Workflow

Workflow for Releasing a New Version of CF-Deployment With a Major Stemcell Bump

Why are we doing this

This is a temporary workflow until we implement the Phase 2 of stemcell bump, which will automatically handle the switch between major/minor stemcell releases.

Workflow

1. Pause the update-releases/acquire-pre-dev-lock-for-update-stemcell-minor CI job.
2. Unpause the update-releases/acquire-all-pre-dev-locks CI job. This will automatically:
   1. Bump the stemcell version in the base cf-deployment.yml manifest
   2. Recompile all base releases against the new version
   3. Push the changes to develop
3. Wait for the change to reach the release-candidate branch of cf-deployment.
4. Notify PM to cut a new version of cf-deployment containing the major stemcell bump.
5. Update the definition of the stemcell-minor-bump-only resource in the update-releases pipeline to include the new major stemcell version number.
6. Pause the update-releases/acquire-all-pre-dev-locks CI job.
7. Unpause the update-releases/acquire-pre-dev-lock-for-update-stemcell-minor CI job.