There are several main reusable workflows that makes release engineering process works The workflows operates with single application from monorepo. So if you have multiple applications in the repo you have to reference the workflows multiple times - one per application
This workflow should be triggered on PR open/syncronized/closed or labeled/unlabeled. It performs Docker build, run tests and deploys application with ECS one or multiple QA environments.
This workflow should be triggered on push into the main branch. It performs Docker build, run tests and deploys application with ECS on multiregion dev environment.
This workflow should be triggered on publishing new release. It promotes exiting Docker build from the main branch to release version and deploy it with ECS on multiregion staging environment.
This workflow should be triggered manually with release version as input. It will check that the docker image for the release version exists and deploy it with ECS on multiregion production environment.
Controllers are reusable workflows that helps to automate interaction between main workflows and GitHub API
The workflow draft new GitHub release. Used as the final step in a main branch workflow to create/update predefined release
The workflow draft new GitHub release. Used as the final step in a main branch workflow to create/update predefined release
This is a glue workflow to connect regular releases' workflow with hotfix workflow. It creates a release branch for each new release version. Used as part of the release workflow.
Promote previous version or build new docker image and test it
Promote docker image to specific release version
Check if there is docker image with specific tag in the ECR