vault backup: 2024-04-09 10:24:45

This commit is contained in:
2024-04-09 10:24:45 +02:00
parent 03ebbf03a9
commit d181ee8d63

View File

@@ -25,7 +25,7 @@ modification-date: Tuesday 9th April 2024 09:49:48
>> Somewhere >> Somewhere
## Core ## Core
In a trunk based game development environment, here's a list of the basic actions taken to make the game go through the whole CI/CD process. 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 ### CI
- MANUAL: create a branch from `main` to code something - MANUAL: create a branch from `main` to code something
- MANUAL: commit and push to this branch - MANUAL: commit and push to this branch
@@ -35,10 +35,11 @@ In a trunk based game development environment, here's a list of the basic action
- AUTO: labelling with `feat`, `fix`, `chore`, optionally `code-review`. If labelled as `code-review`, let it sit. - 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 - AUTO: otherwise, merge to `main` and delete current branch
### CD ### CD
- AUTO: 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/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 - AUTO: build, cook, stage, package and archive the game (development)
- AUTO: run tests on build (acceptance, stress) - AUTO: run tests on build (acceptance, E2E)
- AUTO: on success upload the result to a running build release - AUTO: on success upload the result to a running build release
- NIGHTLY:
--- ---
# References # References