Retrofit to:
- MinorDev, MajorINT, INT, UAT, BugFix, Release branch of current ongoing release (major)
- Is the responsibility of the release manager
- Must be done on a daily basis, with emphasis to take place after a release to production, and for any available work to retrofit.
- MajorDev1s (in plural as there may be more in the future)
- is the responsibility of the developers and Tech Leads.
- Must be done on a daily basis, for any available work to retrofit.
Note : that there is no technical documentation on this topic at the moment, is a known process by tech leads / release manager. Consider the creation of this documentation if the need raises in the future.
For RM:
Example to use below commands to retrofit on VSCode locally and push it to repo:
Bring the latest status of master branch (prod) on our local environment
git checkout master
git pull
# env/minordev - Backpromote
# 1. Bring the latest status of env/minordev branch (on our local environment)
git checkout env/minordev
git pull
# 2. Merge master into env/minordev
git merge master --no-edit
# 3. Push the changes (after closing the screen in vscode)
git push
# 4. Monitor the gitlab execution (a gitlab job was triggered)
# No command here, only manual monitoring
The best way to get IT support is to use the new
Service One Platform.