Nemcio/SCM-Manager
1
0
Fork 0
mirror of https://github.com/scm-manager/scm-manager.git synced 2025-10-26 08:06:09 +01:00
Code Issues Packages Projects Releases Activity

Add documentation about the second build of a hotfix branch

Browse Source 
Squash commits of branch feature/hotfix-release-doc:

- Add documentation about the second build of a hotfix release

- Adjust the important note in hotfix release
This commit is contained in:
Thomas Zerr
2025-05-20 10:36:08 +02:00
parent e671de9325
commit 5c1796c61d
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/en/release-process.md
View File

@@ -258,6 +258,12 @@ released, yet.
6. Double check this all
7. Commit the changes and push the hotfix branch
8. Jenkins will build and release this hotfix with the given version
**Important Note:**
After the first successful run, a second will start and always fail.
This is due to the pipeline updating the tag version and commit / pushing this change to the hotfix branch.
This second build will always fail, but this second build has no impact on whether the release has been successful or not.
9. When Jenkins has finished, fetch the changes (and the new tag)
10. Merge this new Tag into `main` (or fast-forward `main` if possible) and push `main`
(`git checkout main && git pull && git merge hotfix/<new version> && git push`)