GitVersion 6.0.0 taking much longer than 5.12.0 to calculate version #4112

Cheesebaron · 2024-07-23T12:02:23Z

Cheesebaron
Jul 23, 2024

I have a repo where we've been running GitVersion forever and haven't had issues with it up until now.

It seems like switching to 6.0.0 the time to calculate version went from 57 seconds in CI to around 14 minutes.

We are using the GitVersion.Tool to run.

The config we have in place in 5.12.0 looks like this:

branches:
  release:
    regex: ^release[/]
    mode: ContinuousDelivery
    tag: ''
    increment: Patch
    prevent-increment-of-merged-branch-version: true
    track-merge-target: false
    tracks-release-branches: false
    is-release-branch: true
  hotfix:
    regex: ^hotfix[/]
    mode: ContinuousDeployment
    tag: ''
    is-release-branch: true
    track-merge-target: false
    tracks-release-branches: false
    increment: Patch
  feature:
    source-branches: [ 'develop', 'main', 'release', 'feature', 'support', 'hotfix', 'epic' ]
  epic:
    regex: ^epic[/]
    mode: ContinuousDelivery
    tag: '{BranchName}'
    increment: Inherit
    prevent-increment-of-merged-branch-version: false
    track-merge-target: false
    source-branches: [ 'develop', 'main', 'release', 'feature', 'support', 'hotfix', 'epic' ]
    tracks-release-branches: false
    is-release-branch: false
    is-mainline: false
    pre-release-weight: 30000
  develop:
    tag: ci

I tried converting it to 6.0.0 and ended up with this. Which took 43 minutes on my local machine:

workflow: GitFlow/v1
branches:
  release:
    label: ''
    source-branches: [ 'develop', 'main', 'release' ]
  hotfix:
    label: ''
    source-branches: [ 'develop', 'main', 'release' ]
  feature:
    source-branches: [ 'develop', 'release', 'feature', 'support', 'hotfix', 'epic' ]
  epic:
    mode: ManualDeployment
    label: '{BranchName}'
    increment: Inherit
    prevent-increment:
      when-current-commit-tagged: false
    track-merge-message: true
    regex: ^epics?[/-](?<BranchName>.+)
    source-branches: [ 'develop', 'epic' ]
    is-source-branch-for: []
    is-main-branch: false
    pre-release-weight: 30000
  develop:
    label: ci

Then simply removed most of it and ended up with a config like this which takes 2 minutes to complete on my machine. Which is still significantly longer than the older version and it takes around 14 minutes in CI which I really don't want to wait for. The config for this looks like:

workflow: GitFlow/v1
branches:
  release:
    label: ''
  hotfix:
    label: ''
  develop:
    label: ci

I've tried to run with diagnostics enabled, but it doesn't really help me to pinpoint what is increasing the.

Can someone maybe help with where to look at what is causing these performance issues?

HHobeck · 2024-07-23T12:30:12Z

HHobeck
Jul 23, 2024
Maintainer

I think the best thing you can do is to play around with the strategies property and find out if the performance issue is related to a specific strategy implementation or related to how the branch configuration are determined.

6 replies

HHobeck Jul 23, 2024
Maintainer

What do you mean it doesn't take effect!? Does it still take 15 minutes? Please test it with ConfiguredNextVersion.

workflow: GitFlow/v1
NextVersion: 1.0.0
strategies:
- ConfiguredNextVersion

Shouldn't this just directly fall back and give the version 0.1.0?

All version calculation classes are implementing the interface IVersionStrategy and can be controlled by the strategies property.

Cheesebaron Jul 24, 2024
Author

Yeah that doesn't work, getting this error in the log:

Could not build the configuration instance because following exception occurred: 'Property 'NextVersion' not found on type 'GitVersion.Configuration.GitVersionConfiguration'.' Please ensure that the /overrideconfig parameters are correct and the configuration file is in the correct format.

When I have only the Fallback strategy present, it takes 14 minutes locally and seems to be running all the strategies and not just fallback. This is the same if I for instance only specify TaggedCommit.

HHobeck Jul 24, 2024
Maintainer

What about next-version? ;)

HHobeck Jul 24, 2024
Maintainer

Try this:

workflow: ''
next-version: 4.5.6
assembly-versioning-scheme: MajorMinorPatch
assembly-file-versioning-scheme: MajorMinorPatch
tag-prefix: '[vV]?'
version-in-branch-pattern: (?<version>[vV]?\d+(\.\d+)?(\.\d+)?).*
major-version-bump-message: '\+semver:\s?(breaking|major)'
minor-version-bump-message: '\+semver:\s?(feature|minor)'
patch-version-bump-message: '\+semver:\s?(fix|patch)'
no-bump-message: '\+semver:\s?(none|skip)'
tag-pre-release-weight: 60000
commit-date-format: yyyy-MM-dd
merge-message-formats: {}
update-build-number: true
semantic-version-format: Strict
strategies:
- ConfiguredNextVersion
branches:
  develop:
    mode: ContinuousDelivery
    label: alpha
    increment: Minor
    prevent-increment:
      when-current-commit-tagged: false
    track-merge-target: true
    track-merge-message: true
    regex: ^dev(elop)?(ment)?$
    source-branches:
    - main
    is-source-branch-for: []
    tracks-release-branches: true
    is-release-branch: false
    is-main-branch: false
    pre-release-weight: 0
  main:
    label: ''
    increment: Patch
    prevent-increment:
      of-merged-branch: true
    track-merge-target: false
    track-merge-message: true
    regex: ^master$|^main$
    source-branches: []
    is-source-branch-for: []
    tracks-release-branches: false
    is-release-branch: false
    is-main-branch: true
    pre-release-weight: 55000
  release:
    mode: ManualDeployment
    label: beta
    increment: Minor
    prevent-increment:
      of-merged-branch: true
      when-current-commit-tagged: false
    track-merge-target: false
    regex: ^releases?[/-](?<BranchName>.+)
    source-branches:
    - main
    - support
    is-source-branch-for: []
    tracks-release-branches: false
    is-release-branch: true
    is-main-branch: false
    pre-release-weight: 30000
  feature:
    mode: ManualDeployment
    label: '{BranchName}'
    increment: Inherit
    prevent-increment:
      when-current-commit-tagged: false
    track-merge-message: true
    regex: ^features?[/-](?<BranchName>.+)
    source-branches:
    - develop
    - main
    - release
    - support
    - hotfix
    is-source-branch-for: []
    is-main-branch: false
    pre-release-weight: 30000
  pull-request:
    mode: ContinuousDelivery
    label: PullRequest
    increment: Inherit
    prevent-increment:
      of-merged-branch: true
      when-current-commit-tagged: false
    label-number-pattern: '[/-](?<number>\d+)'
    track-merge-message: true
    regex: ^(pull|pull\-requests|pr)[/-]
    source-branches:
    - develop
    - main
    - release
    - feature
    - support
    - hotfix
    is-source-branch-for: []
    pre-release-weight: 30000
  hotfix:
    mode: ManualDeployment
    label: beta
    increment: Inherit
    prevent-increment:
      when-current-commit-tagged: false
    regex: ^hotfix(es)?[/-](?<BranchName>.+)
    source-branches:
    - main
    - support
    is-source-branch-for: []
    is-release-branch: true
    is-main-branch: false
    pre-release-weight: 30000
  support:
    label: ''
    increment: Patch
    prevent-increment:
      of-merged-branch: true
    track-merge-target: false
    regex: ^support[/-](?<BranchName>.+)
    source-branches:
    - main
    is-source-branch-for: []
    tracks-release-branches: false
    is-release-branch: false
    is-main-branch: true
    pre-release-weight: 55000
  unknown:
    mode: ManualDeployment
    label: '{BranchName}'
    increment: Inherit
    prevent-increment:
      when-current-commit-tagged: true
    regex: (?<BranchName>.+)
    source-branches:
    - main
    - develop
    - release
    - feature
    - pull-request
    - hotfix
    - support
    is-source-branch-for: []
    is-main-branch: false
ignore:
  sha: []
mode: ContinuousDelivery
label: '{BranchName}'
increment: Inherit
prevent-increment:
  of-merged-branch: false
  when-branch-merged: false
  when-current-commit-tagged: true
track-merge-target: false
track-merge-message: true
commit-message-incrementing: Enabled
regex: ''
source-branches: []
is-source-branch-for: []
tracks-release-branches: false
is-release-branch: false
is-main-branch: false

Cheesebaron Jul 24, 2024
Author

Well, that kind of works, but this took 2 minutes and 34 seconds to complete.

2024-07-24 09:20:07		INFO [24-07-24 9:20:07:47] Working directory: /Users/tomaszcielecki/git/DrivingRangeApp/build
2024-07-24 09:20:07		INFO [24-07-24 9:20:07:48] Project root is: /Users/tomaszcielecki/git/DrivingRangeApp/
2024-07-24 09:20:07		INFO [24-07-24 9:20:07:48] DotGit directory is: /Users/tomaszcielecki/git/DrivingRangeApp/.git
2024-07-24 09:20:07		INFO [24-07-24 9:20:07:48] Branch from build environment: 
2024-07-24 09:20:07		INFO [24-07-24 9:20:07:50] Found configuration file at '/Users/tomaszcielecki/git/DrivingRangeApp/GitVersion.yml'

...

2024-07-24 09:22:41		INFO [24-07-24 9:22:41:39] -< End: Fetching the base versions for version calculation... (Took: 153,298.86ms) >-
2024-07-24 09:22:41		INFO [24-07-24 9:22:41:39] -------------------------------------------------------
2024-07-24 09:22:41		INFO [24-07-24 9:22:41:40] Base version used: NextVersion in GitVersion configuration file: Take '4.5.6'
2024-07-24 09:22:41		INFO [24-07-24 9:22:41:40] -------------------------------------------------------
2024-07-24 09:22:41		INFO [24-07-24 9:22:41:40] -< Begin: Using manual deployment workflow to calculate the incremented version. >-

Cheesebaron · 2024-07-25T06:49:03Z

Cheesebaron
Jul 25, 2024
Author

Sorry, cannot spend more time messing around with this. So I've migrated over to use NerdBank.GitVersioning.

However, seems like there have been some changes which, at least in some of my repo's, cause GitVersion.Tool to run for much longer when calculating the version.

2 replies

HHobeck Jul 25, 2024
Maintainer

@Cheesebaron: I'm not sure why it is not common in the open source community to say thank you. At least when someone responding after 30 minutes it would be very grateful to receive a recognition.

It is sad you are switching to another tool. But that is okay if it suits your needs.

All the best from me.

Cheesebaron Jul 25, 2024
Author

I didn't mean anything negative with this, just a reality of having to focus on something else than keep digging into this specific issue. I wish I could spare more time to help investigate this issue, but I cannot do so at this point.

I do appreciate all the help you've provided and in a very timely manner. So thank you!

When I have more time to dig around here I will reopen the investigation. I am still using GitVersion.Tool elsewhere, but in this particular repo, it was just slowing us down and unfortunately I cannot share that repo with you either.

Thanks again!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

GitVersion 6.0.0 taking much longer than 5.12.0 to calculate version #4112

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments 8 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{title}}

Select a reply

GitVersion 6.0.0 taking much longer than 5.12.0 to calculate version #4112

Cheesebaron Jul 23, 2024

Replies: 2 comments · 8 replies

HHobeck Jul 23, 2024 Maintainer

HHobeck Jul 23, 2024 Maintainer

Cheesebaron Jul 24, 2024 Author

HHobeck Jul 24, 2024 Maintainer

HHobeck Jul 24, 2024 Maintainer

Cheesebaron Jul 24, 2024 Author

Cheesebaron Jul 25, 2024 Author

HHobeck Jul 25, 2024 Maintainer

Cheesebaron Jul 25, 2024 Author

Cheesebaron
Jul 23, 2024

Replies: 2 comments 8 replies

HHobeck
Jul 23, 2024
Maintainer

HHobeck Jul 23, 2024
Maintainer

Cheesebaron Jul 24, 2024
Author

HHobeck Jul 24, 2024
Maintainer

HHobeck Jul 24, 2024
Maintainer

Cheesebaron Jul 24, 2024
Author

Cheesebaron
Jul 25, 2024
Author

HHobeck Jul 25, 2024
Maintainer

Cheesebaron Jul 25, 2024
Author