Continuous Deployment
DRAFT
- 1 Overview
- 2 Continuous Integration
- 2.1 Type of Commits
- 2.2 Tagging
- 2.2.1 Type of tagging
- 2.3 Artefacts
- 3 Continuous Deployment
- 3.1 Environments
Overview
This document covers proposal for CI tagging strategy for continuous integration and deployment. Currently we have different release branches and gitgub workflows to release to different environments. We want to streamline process and reduce code duplication to improve efficiency.
Continuous Integration
Type of Commits
Types of commits that will generate artefacts:
pr merges to master branch
Tagging
master branch with milestones/releases tags
docker image
Type of tagging
stable tags (semantic versioning)
unique tags (commit hash)
Samples:
| Repo(Master) | Docker Image |
---|---|---|
Alpha(each commit on master) | - | alpha-latest, bec53s, alpha-buildnumber |
Beta | beta-2020.05.12 | beta-latest, bec53s, beta-buildnumber |
Gamma | gamma-2020.05.10 | gamma-latest, bec53s, gamma-buildnumber |
Live | v1.0, v1.1, v1.2 | latest, bec53s, v-1.1, v-1.2 |
Artefacts
Currently, we just have docker artefact published to ECR. The infrastructure is already set up and sits in the same repo under x.
Continuous Deployment
Environments
List of Environments.
Managing Access to open platforms | Alpha.voluntarily.nz