-
|
Hello, I've just moved our projects to GitVersion, but I'm having trouble getting it to work as I want it. We're using Azure DevOps and the gitversion tasks, and we're working using the GitFlow workflow. Which means we use We currently have a repo with 4 tags, where the latest tag is What I am expecting GitVersion to produce is this:
Tags:
Determine Version outputThis output comes from a pipeline that runs on PRs into Pipeline determine versionGitVersion.ymlmode: ContinuousDelivery
increment: Inherit
major-version-bump-message: '\+ver:\s?(breaking|major)'
minor-version-bump-message: '\+ver:\s?(feature|minor)'
patch-version-bump-message: '\+ver:\s?(fix|patch)'
no-bump-message: '\+ver:\s?(none|skip)'
tag-prefix: '[vV]'
assembly-versioning-scheme: MajorMinorPatch
assembly-file-versioning-scheme: MajorMinorPatchTag
assembly-informational-format: '{InformationalVersion}'
commit-message-incrementing: Enabled
ignore:
commits-before: 2021-11-01T00:00:00
branches:
main:
regex: ^master$|^main$
mode: ContinuousDelivery
tag: ''
increment: None
source-branches: ['develop', 'release']
prevent-increment-of-merged-branch-version: true
is-release-branch: false
is-mainline: true
tracks-release-branches: false
release:
regex: ^release(s)?[/-]
mode: ContinuousDelivery
tag: ''
increment: Patch
source-branches: ['develop']
prevent-increment-of-merged-branch-version: true
is-release-branch: true
tracks-release-branches: false
is-mainline: false
develop:
regex: ^develop$
mode: ContinuousDelivery
tag: ''
increment: Minor
source-branches: []
prevent-increment-of-merged-branch-version: false
track-merge-target: true
tracks-release-branches: true
is-release-branch: false
is-mainline: false
pre-release-weight: 0
feature:
regex: ^feature(s)?[/-]
mode: ContinuousDelivery
tag: ''
increment: Patch
source-branches: [ 'develop', 'master', 'release', 'feature', 'support', 'hotfix' ]
track-merge-target: false
tracks-release-branches: false
prevent-increment-of-merged-branch-version: false
is-release-branch: false
is-mainline: false
pull-request:
regex: ^(pull|pull\-requests|pr)[/-]
mode: ContinuousDelivery
tag: PR
increment: Patch
source-branches: ['develop', 'feature', 'hotfix']
tracks-release-branches: false
prevent-increment-of-merged-branch-version: false
is-release-branch: false
is-mainline: false
hotfix:
regex: ^hotfix(es)?[/-]
mode: ContinuousDelivery
tag: ''
increment: Patch
source-branches: ['develop', 'master']
tracks-release-branches: false
prevent-increment-of-merged-branch-version: false
is-release-branch: false
is-mainline: false |
Beta Was this translation helpful? Give feedback.
Answered by
asbjornu
Dec 8, 2021
Replies: 1 comment 8 replies
-
|
A good way to start debugging GitVersion is to delete |
Beta Was this translation helpful? Give feedback.
8 replies
-
|
Okay... I think I've just been stupid here, i now see that the version is infact correct... Tags are My fault, I wasn't looking correctly! |
Beta Was this translation helpful? Give feedback.
-
|
I'm glad you figured it out! 👍🏼 |
Beta Was this translation helpful? Give feedback.
-
|
There seems to still be one issue though, I'm expecting every commit to |
Beta Was this translation helpful? Give feedback.
-
|
I'd expect a new commit to generate |
Beta Was this translation helpful? Give feedback.
-
|
You get that behaviour with |
Beta Was this translation helpful? Give feedback.
Answer selected by
Fronix
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A good way to start debugging GitVersion is to delete
GitVersion.yml. How does that affect the versioning?