This repository was archived by the owner on Sep 25, 2025. It is now read-only.
generated from bcgov/quickstart-openshift
-
Notifications
You must be signed in to change notification settings - Fork 0
Deployment Process
afwilcox edited this page Apr 25, 2024
·
7 revisions
- Create a PR for your change in this repository.
- Once approved, this will push changes to the Gitops repo here: https://github.com/[bcgov-c/tenant-gitops-dc0a4a](https://github.com/bcgov-c/tenant-gitops-dc0a4a)
- Argo will see the changes and deploy to Emerald.
- There are 5 slots available in the development environment that can be deployed to. These slots are referred to as dev-1, dev-2, ..., dev-5. In order to determine which slot will be used the pipeline will use your PR# and perform the following calculation:
- (PR# mod 5) + 1
- Example 1: if your PR number is 30: (30 mod 5) + 1 = 0 + 1 = dev-1
- Example 2: if your PR number is 98: (98 mod 5) + 1 = 3 + 1 = dev-4
- In order to mitigate slot conflicts (for example: if PR 30 and PR 35 are both active at the same time) all deployments to the dev environment must be manually approved. A migration to dev should not be approved if an open PR is already occupying the slot.