Incrementing on PreReleaseTag #4445
Unanswered
john-warren-dspp
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Prerequisites
GitVersion package
AzureDevops task
GitVersion version
6
Operating system
Linux
What are you seeing?
I am currently upgrading our ADO pipeline gitversion task to version 6 and have the following configuration file. However the we are still getting the serversion incrementing on the PreReleaseTag,
GitVersion executed successfully
Async Command Start: Update Build Number
Update build number to 2.0.19-1 for build 80882
Async Command End: Update Build Number
Finishing: Calculate Version
and not the patch as we believe we have specified in the git configuration file below
workflow: GitHubFlow/v1 # Only add this if you want every version to be created automatically on your main branch.
major-version-bump-message: "^(build|chore|ci|docs|feat|fix|perf|refactor|revert|style|test)(\([\w\s-]\))?(!:|:.\n\n((.+\n)+\n)?BREAKING CHANGE:\s.+)"
minor-version-bump-message: "^(feat)(\([\w\s-]\))?:"
patch-version-bump-message: "." # Catch-all rule for patch version bump"
Set default increment to patch if no other pattern matches
branches:
main:
regex: ^main$
increment: Patch
develop:
regex: ^develop$
increment: Patch
feature:
regex: ^features?[/-]
increment: Patch
bugfix:
regex: ^bugfix(es)?[/-]
increment: Patch
release:
regex: ^releases?[/-]
increment: Patch
hotfix:
regex: ^hotfix(es)?[/-]
increment: Patch
support:
regex: ^support[/-]
increment: Patch
pull-request:
regex: ^pull-requests?[/-]
increment: Patch
What is expected?
Async Command Start: Update Build Number
Update build number to 2.0.16 for build 80874
Async Command End: Update Build Number
Finishing: Calculate Version
Steps to Reproduce
upgrade to gitversion 6 and gitversiontask2 in ADO pipeline
RepositoryFixture Test
No response
Output log or link to your CI build (if appropriate).
Beta Was this translation helpful? Give feedback.
All reactions