vault backup: 2024-04-09 10:28:17
This commit is contained in:
@@ -30,16 +30,19 @@ In a trunk based UE game development environment, here's a list of the basic act
|
||||
- MANUAL: create a branch from `main` to code something
|
||||
- MANUAL: commit and push to this branch
|
||||
- AUTO: build the game, run the game (null hypothesis test)
|
||||
- AUTO: run basic tests (unit/functional), any test that can be done quickly in a matter of minutes max.
|
||||
- AUTO: run basic tests (unit/functional).
|
||||
- AUTO: on success, create a PR.
|
||||
- AUTO: labelling with `feat`, `fix`, `chore`, optionally `code-review`. If labelled as `code-review`, let it sit.
|
||||
- AUTO: otherwise, merge to `main` and delete current branch
|
||||
- METRIC: This should take minutes max.
|
||||
### CD
|
||||
- AUTO/MANUAL: on PR merge, if the PR is `feat`, bump the minor version tag. if the PR is `fix` or `chore`, bump the patch version.
|
||||
- AUTO: build, cook, stage, package and archive the game (development)
|
||||
- AUTO: run tests on build (acceptance, E2E)
|
||||
- AUTO: on success upload the result to a running build release
|
||||
- NIGHTLY:
|
||||
- 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, cook, stage, package and archive the game (production)
|
||||
|
||||
---
|
||||
# References
|
||||
Reference in New Issue
Block a user