Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Performance issue in pre 6.0.0-beta.1 #3442

Closed
facusantillo opened this issue Mar 16, 2023 · 2 comments
Closed

[Bug] Performance issue in pre 6.0.0-beta.1 #3442

facusantillo opened this issue Mar 16, 2023 · 2 comments
Labels

Comments

@facusantillo
Copy link

facusantillo commented Mar 16, 2023

Describe the bug
Moving pipeline from release 6.0.0-alpha.1 to 6.0.0-beta.1 with same definition files takes 5x times more to calculate the version

Expected Behavior

Calculate version in release 6.0.0-alpha.1 took around 2 minutes.

Actual Behavior

In version 6.0.0-beta.1 took approx 10 min

Context

This is a little bit tricky. In repos with 200+ tags with lots of PR's in the alpha version calculating the version is almost instant while the beta takes too long to finish. We are using the continuous delivery mode.

Your Environment

  • Version Used: 6.0.0-beta.1
  • Operating System and version: Azure DevOps, Self-Hosted Agent with Windows-2022 as vmImage
  • Link to your project: it's private project from the organization
  • Link to your CI build (if appropriate): it's private project from the organization

GitVersion YAML:

mode: ContinuousDelivery
commit-message-incrementing: enabled

branches:
  release:
    mode: ContinuousDelivery
    regex: ^release?
    label: 'rc'
    increment: Patch
    prevent-increment-of-merged-branch-version: false
    tracks-release-branches: false
    track-merge-target: false
    source-branches:
      - develop
      - hotfix
    is-release-branch: true
    is-mainline: false

  develop:
    mode: ContinuousDelivery
    regex: ^develop$
    prevent-increment-of-merged-branch-version: true
    label: 'rc'
    tracks-release-branches: false
    track-merge-target: true
    increment: Minor
    is-release-branch: false
    is-mainline: true
    source-branches: []
    pre-release-weight: 60000

  hotfix:
    mode: ContinuousDelivery
    regex: ^hotfix?
    prevent-increment-of-merged-branch-version: false
    label: hotfix
    tracks-release-branches: true
    track-merge-target: true
    increment: Patch
    is-release-branch: false
    is-mainline: false    
    source-branches:
      - develop
      - release
    pre-release-weight: 30000

  pull-request:
    mode: ContinuousDelivery
    label: 'PR'
    increment: Inherit
    regex: ^pull?
    is-release-branch: false
    prevent-increment-of-merged-branch-version: false
    is-mainline: false
    tracks-release-branches: false
    track-merge-target: false
    source-branches:
      - feature
      - hotfix
      - develop
      - release
    pre-release-weight: 30000
    
  feature:
    mode: ContinuousDelivery
    label: 'rc'
    increment: Inherit
    regex: ^feature?
    is-release-branch: false
    prevent-increment-of-merged-branch-version: false
    is-mainline: false
    tracks-release-branches: false
    track-merge-target: true
    source-branches:
      - feature
      - hotfix
      - develop
      - release
    pre-release-weight: 30000

Logs:

gitlog alpha version.txt
gitlog beta version.txt

@HHobeck
Copy link
Contributor

HHobeck commented Mar 17, 2023

First I would like to thank you for reporting your experience with the pre release version 6.0.0-beta.1. I have seen some issues (like #3212) which are related to performance but they are pending. Please don't get my point wrong: But in my opinion it's not so pleasant to create a bug and say it's 10 times higher without providing any information about your environment. You know that we are working on this project in our spare time right!? It's a community work and you are part of it.

May I ask you to help us with the following one or more points:

  • Give background information about your context/environment
  • Find out where the problem might be located (Is it because of so many tags? Is it because of so many branches? Is it because you are using a special mode?)
  • Create a repository which can be used for improving the performance
  • Statistic how the complexity is in different circumstances (https://en.wikipedia.org/wiki/Time_complexity)

@HHobeck HHobeck added this to the 6.x milestone Mar 17, 2023
@facusantillo
Copy link
Author

Hi @HHobeck sorry for the trouble,

I completed the issue with all the info that I currently have, I'll try to dig into it 'cause not sure what is causing it

Thanks

@arturcic arturcic modified the milestones: 6.x, 6.0.0-beta.3 Jun 26, 2023
@HHobeck HHobeck removed this from the 6.0.0-beta.3 milestone Jul 21, 2023
@GitTools GitTools deleted a comment from arturcic Jul 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants