You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Release process is automated in following way:
1) with every build, we update files with appropriate version number before we deploy
2) when build is executed on a branch named `release/v1.2.3-something` then additional steps are taken:
- project version in files: `sonar-project.properties`, `VERSION` is updated from the version number derived from release branch
- changes on those two files are committed and and pushed - this should happen only once, when the release branch is initially created on the main repo
3) To create a release, just create a tag on the code to be released. The tag name must match the regex pattern: `^v[0-9]+\.[0-9]+\.[0-9]+.*$`
- When a tag build is executed, the documentation is built and files are uploaded to the tag.
- The version number is derived from the tag name.
0 commit comments