Environments
- Each environment is deployed independently (e.g. separate servers, DBs, etc).
- Each environment deploys new code included in the release once the automated tests for that particular release-commit pass successfully.
The release-candidate and release branches below apply to apps on the
legacy release process. Apps on the
Concourse release workflow
have neither branch: RC and Production deploy the same image, built from a
releases/<version> branch and tagged with the calendar version.
Environment Name
|
|
| Git Branch |
The Github branch that the environment has deployed. |
| Purpose |
The purpose of the environment. |
| Expectations |
Expectations for environment usage and processes. |
CI
|
|
| Git Branch |
main or master |
| Purpose |
Testing code from main or master in a deployed environment prior to being included in a release candidate and release process. |
| Expectations |
Code is tested and functionality confirmed shortly after releasing to CI. |
RC
|
|
| Git Branch |
release-candidate |
| Purpose |
Functional testing prior to production deployment.
Acceptance testing by stakeholders.
Demonstration environment. |
| Expectations |
Mock data can be created. Some risk is acceptable by deploying code that cannot be tested locally by a developer. |
Production
|
|
| Git Branch |
release |
| Purpose |
Environment for end users. |
| Expectations |
Limit creation of mock data. Code and functionality should pose minimal risk. |