Pipeline
A release is the standard process for promoting features from dev to test, and then to production. To create a release, start by creating a branch (off of main) named /release/{release_name} (e.g., /release/2.12, following the numbering naming convention).
All feature branches for the release should be branched off of the release branch, such as /release/2.12/ce-123.
Dev
Creating a PR of your feature branch into the release branch will automatically deploy to the DEV environment in OpenShift.
Test
Once the PR is approved and merged, it automatically triggers a deployment to the TEST environment.
Prod
Deployment to Production is a multi step process:
-
Create a PR to merge the release branch into main.
-
Once the PR is reviewed and approved launch the 'Release to Production' GitHub action. This action takes a single parameter, the name of the release branch (e.g.
release/2.12)
- This step may be automated in the future. Issue a commit to the gitops repo updating the .outputs/values-prod file with the tag that resulted from the previous step. The tag is the number of the last pull request deployed to the test environment and can be confirmed by reviewing the versions of any artifact in github:
- Review the diff in argo and manually start the production sync.
