1.8 KiB
1.8 KiB
tags, relates-to, creation-date, modification-date
| tags | relates-to | creation-date | modification-date | ||
|---|---|---|---|---|---|
|
2024-04-09 09:46 | Tuesday 9th April 2024 09:49:48 |
Git CI/CD
Compass
[!multi-column]
[!info]+ Comes from Somewhere
[!success]+ Similar to Something
[!danger]+ Competes with Something
[!seealso]+ Leads to Somewhere
Core
In a trunk based UE game development environment, here's a list of the basic actions taken to make the game go through the whole CI/CD process.
CI
- MANUAL: create a branch from
mainto code something - MANUAL: commit and push to this branch
- AUTO: labelling with either
feat, chore, docs, fix, refactor, or test. - AUTO: can also be additionally
skip-ciand/orcode-review. If labelled ascode-review, let it sit. - AUTO: if not
skip-ci, build the game, run the game (null hypothesis test) - AUTO: run basic pre-package tests (unit/functional).
- AUTO: on success, create a PR.
- AUTO: otherwise, merge to
mainand delete current branch - METRIC: This should take minutes max.
- AUTO: labelling with either
CD
- AUTO/MANUAL: on PR merge, if the PR is
feat, bump the minor version tag. if the PR isfixorchore, bump the patch version. Ifskip-ci, stop there.- AUTO: build, cook, stage, package and archive the game (development)
- AUTO: run tests on package (acceptance, E2E)
- AUTO: on success upload the result to a running build release.
- METRIC: This should take minutes max.
- NIGHTLY/MANUAL: either each night or on manual workflow trigger, make a complete build.
- AUTO: build the game, run the game.
- AUTO: run all pre-package tests.
- AUTO: build, cook, stage, package and archive the game (production)
- AUTO: run all package tests.
- AUTO: create a unique release with a release note and checkboxes.
- AUTO: publish on steam (or other).