[Continuos Delivery] Dev branch and release branch with same commit

[DanieleSky]

Hi,
I've a repo with main and dev branches. I'm using GitFlow strategy on Gitlab.
From dev I opened the release's branch "releases-1.1.0" and tag the delivery with tag "v1.1.0-beta.1"
In this case I've got the same commit on dev and releases branches.

Gitversion ignored my tag and use the configuration of dev branches, with this motivation:
"Choosing refs/heads/dev as it is the only branch without / or - in it. Move one of the branches along a commit to remove warning"

Why there is this behaviour?

This the entire log:

INFO [02/12/24 11:23:15:16] Working directory: /home/gitlab-runner/builds/DkRhZunrd/0/v4r/dinamo/dinamo-web-api-gateway
INFO [02/12/24 11:[23](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L23):15:17] Project root is: /home/gitlab-runner/builds/DkRhZunrd/0/v4r/dinamo/dinamo-web-api-gateway/
INFO [02/12/[24](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L24) 11:23:15:17] DotGit directory is: /home/gitlab-runner/builds/DkRhZunrd/0/v4r/dinamo/dinamo-web-api-gateway/.git
INFO [02/12/24 11:23:15:17] Branch from build environment: 
INFO [02/12/24 11:23:15:17] -< Begin: Normalizing git directory for branch '' >-
  INFO [02/12/24 11:23:15:23] One remote found (origin -> 'http://gitlab-ci-token:*******@gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway.git').
  INFO [02/12/24 11:23:15:23] Skipping fetching, if GitVersion does not calculate your version as expected you might need to allow fetching or use dynamic repositories
  INFO [02/12/24 11:23:15:[25](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L25)] Skipping update of 'refs/remotes/origin/dev' as it already matches the remote ref.
  INFO [02/12/24 11:23:15:25] Skipping update of 'refs/remotes/origin/hotfix/#5181' as it already matches the remote ref.
  INFO [02/12/24 11:23:15:25] Skipping update of 'refs/remotes/origin/main' as it already matches the remote ref.
  INFO [02/12/24 11:23:15:25] Skipping update of 'refs/remotes/origin/releases-1.1.0' as it already matches the remote ref.
  INFO [02/12/24 11:23:15:[26](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L26)] HEAD is detached and points at commit '83a8f07a1ebd[28](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L28)7e7c38de7e75bf419d45b821eb'.
  INFO [02/12/24 11:23:15:26] Local Refs:
refs/heads/DEV (572a040edd77cc79f0d159928948df4cf79383da)
refs/heads/dev (83a8f07a1ebd287e7c38de7e75bf419d45b821eb)
refs/heads/dev-#5181 (d256b0b5777fa88821590c3d83e7b652bbd991c6)
refs/heads/hotfix/#5181 (d256b0b5777fa88821590c3d83e7b652bbd991c6)
refs/heads/main (54037dca79db25a11c1a46b3314d5815d9ea66cc)
refs/heads/releases-1.1.0 (83a8f07a1ebd287e7c38de7e75bf419d45b821eb)
refs/pipelines/1216 (d256b0b5777fa88821590c3d83e7b652bbd991c6)
refs/pipelines/1217 (d256b0b5777fa88821590c3d83e7b652bbd991c6)
refs/pipelines/1235 (83a8f07a1ebd287e7c38de7e75bf419d45b821eb)
refs/pipelines/1236 (83a8f07a1ebd287e7c38de7e75bf419d45b821eb)
refs/pipelines/1237 (83a8f07a1ebd287e7c38de7e75bf419d45b821eb)
refs/pipelines/620 (572a040edd77cc79f0d159928948df4cf79383da)
refs/pipelines/621 (54037dca79db25a11c1a46b3314d5815d9ea66cc)
refs/pipelines/624 (54037dca79db25a11c1a46b3314d5815d9ea66cc)
refs/pipelines/672 (54037dca79db25a11c1a46b3314d5815d9ea66cc)
refs/remotes/origin/dev (83a8f07a1ebd287e7c38de7e75bf419d45b821eb)
refs/remotes/origin/hotfix/#5181 (d256b0b5777fa88821590c3d83e7b652bbd991c6)
refs/remotes/origin/main (54037dca79db25a11c1a46b3314d5815d9ea66cc)
refs/remotes/origin/releases-1.1.0 (83a8f07a1ebd287e7c38de7e75bf419d45b821eb)
refs/tags/v1.0.0 (54037dca79db25a11c1a46b3314d5815d9ea66cc)
refs/tags/v1.1.0-beta.1 (83a8f07a1ebd287e7c38de7e75bf419d45b821eb)
  WARN [02/12/24 11:23:15:26] Found more than one local branch pointing at the commit '83a8f07a1ebd287e7c38de7e75bf419d45b821eb' (refs/heads/dev, refs/heads/releases-1.1.0).
  WARN [02/12/24 11:23:15:26] Choosing refs/heads/dev as it is the only branch without / or - in it. Move one of the branches along a commit to remove warning
INFO [02/12/24 11:23:15:[30](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L30)] -< End: Normalizing git directory for branch '' (Took: 117.04ms) >-
INFO [02/12/24 11:23:15:[31](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L31)] -< Begin: Loading version variables from disk cache file /home/gitlab-runner/builds/DkRhZunrd/0/v4r/dinamo/dinamo-web-api-gateway/.git/gitversion_cache/E247DF9880FCAA6634A517A424D2E6640C8DA38F >-
  INFO [02/12/24 11:23:15:31] Cache file /home/gitlab-runner/builds/DkRhZunrd/0/v4r/dinamo/dinamo-web-api-gateway/.git/gitversion_cache/E247DF9880FCAA6634A517A424D2E6640C8DA38F not found.
INFO [02/12/24 11:23:15:31] -< End: Loading version variables from disk cache file /home/gitlab-runner/builds/DkRhZunrd/0/v4r/dinamo/dinamo-web-api-gateway/.git/gitversion_cache/E247DF9880FCAA6634A517A424D2E6640C8DA38F (Took: 0.13ms) >-
INFO [02/12/24 11:23:15:[32](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L32)] Using latest commit on specified branch
INFO [02/12/24 11:23:15:68] Running against branch: dev ('83a8f07' - Merge branch 'hotfix/#5181' into 'dev')
INFO [02/12/24 11:23:15:68] Current commit is tagged with version 1.1.0-beta.1, version calculation is for meta data only.
INFO [02/12/24 11:23:15:68] -< Begin: Fetching the base versions for version calculation... >-
  INFO [02/12/24 11:23:15:69] Calculating base versions for 'dev'
  INFO [02/12/24 11:23:15:69] -< Begin: [Using 'ConfigNextVersionVersionStrategy' strategy] >-
  INFO [02/12/24 11:23:15:69] -< End: [Using 'ConfigNextVersionVersionStrategy' strategy] (Took: 0.72ms) >-
  INFO [02/12/24 11:23:15:69] -< Begin: [Using 'MergeMessageVersionStrategy' strategy] >-
  INFO [02/12/24 11:23:15:72] -< End: [Using 'MergeMessageVersionStrategy' strategy] (Took: 24.93ms) >-
  INFO [02/12/24 11:23:15:72] -< Begin: [Using 'TaggedCommitVersionStrategy' strategy] >-
    INFO [02/12/24 11:23:15:74] -< Begin: Getting tagged semantic versions on branch 'refs/heads/dev'. TagPrefix: [vV]? and Format: Strict >-
      INFO [02/12/24 11:23:15:74] Getting tagged semantic versions. TagPrefix: [vV]? and Format: Strict
    INFO [02/12/24 11:23:15:75] -< End: Getting tagged semantic versions on branch 'refs/heads/dev'. TagPrefix: [vV]? and Format: Strict (Took: 9.73ms) >-
    INFO [02/12/24 11:23:15:75] -< Begin: Getting tagged semantic versions by track merge target 'refs/heads/dev'. TagPrefix: [vV]? and Format: Strict >-
    INFO [02/12/24 11:23:15:75] -< End: Getting tagged semantic versions by track merge target 'refs/heads/dev'. TagPrefix: [vV]? and Format: Strict (Took: 3.15ms) >-
    INFO [02/12/24 11:23:15:75] -< Begin: Getting tagged semantic versions of release branches. TagPrefix: [vV]? and Format: Strict >-
      INFO [02/12/24 11:23:15:76] -< Begin: Getting tagged semantic versions on branch 'refs/heads/hotfix/#5181'. TagPrefix: [vV]? and Format: Strict >-
      INFO [02/12/24 11:23:15:76] -< End: Getting tagged semantic versions on branch 'refs/heads/hotfix/#5181'. TagPrefix: [vV]? and Format: Strict (Took: 0.46ms) >-
      INFO [02/12/24 11:23:15:76] -< Begin: Getting tagged semantic versions on branch 'refs/heads/releases-1.1.0'. TagPrefix: [vV]? and Format: Strict >-
      INFO [02/12/24 11:23:15:76] -< End: Getting tagged semantic versions on branch 'refs/heads/releases-1.1.0'. TagPrefix: [vV]? and Format: Strict (Took: 0.48ms) >-
      INFO [02/12/24 11:23:15:76] -< Begin: Getting tagged semantic versions on branch 'refs/remotes/origin/hotfix/#5181'. TagPrefix: [vV]? and Format: Strict >-
      INFO [02/12/24 11:23:15:76] -< End: Getting tagged semantic versions on branch 'refs/remotes/origin/hotfix/#5181'. TagPrefix: [vV]? and Format: Strict (Took: 0.39ms) >-
      INFO [02/12/24 11:23:15:76] -< Begin: Getting tagged semantic versions on branch 'refs/remotes/origin/releases-1.1.0'. TagPrefix: [vV]? and Format: Strict >-
      INFO [02/12/24 11:23:15:76] -< End: Getting tagged semantic versions on branch 'refs/remotes/origin/releases-1.1.0'. TagPrefix: [vV]? and Format: Strict (Took: 0.44ms) >-
    INFO [02/12/24 11:23:15:76] -< End: Getting tagged semantic versions of release branches. TagPrefix: [vV]? and Format: Strict (Took: 8.40ms) >-
    INFO [02/12/24 11:23:15:76] -< Begin: Getting tagged semantic versions of mainline branches. TagPrefix: [vV]? and Format: Strict >-
      INFO [02/12/24 11:23:15:77] -< Begin: Getting tagged semantic versions on branch 'refs/heads/main'. TagPrefix: [vV]? and Format: Strict >-
      INFO [02/12/24 11:23:15:77] -< End: Getting tagged semantic versions on branch 'refs/heads/main'. TagPrefix: [vV]? and Format: Strict (Took: 0.32ms) >-
      INFO [02/12/24 11:23:15:77] -< Begin: Getting tagged semantic versions on branch 'refs/remotes/origin/main'. TagPrefix: [vV]? and Format: Strict >-
      INFO [02/12/24 11:23:15:77] -< End: Getting tagged semantic versions on branch 'refs/remotes/origin/main'. TagPrefix: [vV]? and Format: Strict (Took: 0.32ms) >-
    INFO [02/12/24 11:23:15:77] -< End: Getting tagged semantic versions of mainline branches. TagPrefix: [vV]? and Format: Strict (Took: 3.76ms) >-
    INFO [02/12/24 11:23:15:77] Git tag 'v1.0.0': 1.0.0 with commit source '54037dca79db25a11c1a46b[33](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L33)14d5815d9ea66cc'
    INFO [02/12/24 11:23:15:79] Git tag 'v1.0.0': 1.0.0 with commit source '54037dca79db25a11c1a46b3314d5815d9ea66cc'
    INFO [02/12/24 11:23:15:79] Git tag 'v1.0.0': 1.0.0 with commit source '54037dca79db25a11c1a46b3314d5815d9ea66cc'
    INFO [02/12/24 11:23:15:79] Git tag 'v1.0.0': 1.0.0 with commit source '54037dca79db25a11c1a46b3314d5815d9ea66cc'
    INFO [02/12/24 11:23:15:79] Git tag 'v1.0.0': 1.0.0 with commit source '54037dca79db25a11c1a46b3314d5815d9ea66cc'
    INFO [02/12/24 11:23:15:79] Git tag 'v1.0.0': 1.0.0 with commit source '54037dca79db25a11c1a46b3314d5815d9ea66cc'
    INFO [02/12/24 11:23:15:79] Git tag 'v1.0.0': 1.0.0 with commit source '54037dca79db25a11c1a46b3314d5815d9ea66cc'
    INFO [02/12/24 11:23:15:79] Git tag 'v1.0.0': 1.0.0 with commit source '54037dca79db25a11c1a46b3314d5815d9ea66cc'
    INFO [02/12/24 11:23:15:80] Git tag 'v1.0.0': 1.0.0 with commit source '54037dca79db25a11c1a46b3314d5815d9ea66cc'
  INFO [02/12/24 11:23:15:80] -< End: [Using 'TaggedCommitVersionStrategy' strategy] (Took: 75.74ms) >-
  INFO [02/12/24 11:23:15:80] -< Begin: [Using 'TrackReleaseBranchesVersionStrategy' strategy] >-
    INFO [02/12/24 11:23:15:80] -< Begin: Finding merge base between 'hotfix/#5181' and 'dev'. >-
      INFO [02/12/24 11:23:15:81] Found merge base of ''54037dc' - Merge branch 'DEV' into 'main''
      INFO [02/12/24 11:23:15:82] Merge base of 'hotfix/#5181' and 'dev' is ''54037dc' - Merge branch 'DEV' into 'main''
    INFO [02/12/24 11:23:15:82] -< End: Finding merge base between 'hotfix/#5181' and 'dev'. (Took: 12.99ms) >-
    INFO [02/12/24 11:23:15:83] -< Begin: Finding merge base between 'releases-1.1.0' and 'dev'. >-
      INFO [02/12/24 11:23:15:83] Found merge base of ''83a8f07' - Merge branch 'hotfix/#5181' into 'dev''
      INFO [02/12/24 11:23:15:83] Merge base of 'releases-1.1.0' and 'dev' is ''83a8f07' - Merge branch 'hotfix/#5181' into 'dev''
    INFO [02/12/24 11:23:15:83] -< End: Finding merge base between 'releases-1.1.0' and 'dev'. (Took: 0.65ms) >-
    INFO [02/12/24 11:23:15:83] -< Begin: Finding branch source of 'releases-1.1.0' >-
      INFO [02/12/24 11:23:15:84] -< Begin: Finding merge base between 'releases-1.1.0' and 'main'. >-
        INFO [02/12/24 11:23:15:84] Found merge base of ''54037dc' - Merge branch 'DEV' into 'main''
        INFO [02/12/24 11:23:15:84] Merge base of 'releases-1.1.0' and 'main' is ''54037dc' - Merge branch 'DEV' into 'main''
      INFO [02/12/24 11:23:15:84] -< End: Finding merge base between 'releases-1.1.0' and 'main'. (Took: 0.76ms) >-
      INFO [02/12/24 11:23:15:84] -< Begin: Finding merge base between 'releases-1.1.0' and 'origin/dev'. >-
        INFO [02/12/24 11:23:15:84] Found merge base of ''83a8f07' - Merge branch 'hotfix/#5181' into 'dev''
        INFO [02/12/24 11:23:15:84] Merge base of 'releases-1.1.0' and 'origin/dev' is ''83a8f07' - Merge branch 'hotfix/#5181' into 'dev''
      INFO [02/12/24 11:23:15:84] -< End: Finding merge base between 'releases-1.1.0' and 'origin/dev'. (Took: 0.56ms) >-
      INFO [02/12/24 11:23:15:84] -< Begin: Finding merge base between 'releases-1.1.0' and 'origin/main'. >-
        INFO [02/12/24 11:23:15:84] Found merge base of ''54037dc' - Merge branch 'DEV' into 'main''
        INFO [02/12/24 11:23:15:84] Merge base of 'releases-1.1.0' and 'origin/main' is ''54037dc' - Merge branch 'DEV' into 'main''
      INFO [02/12/24 11:23:15:84] -< End: Finding merge base between 'releases-1.1.0' and 'origin/main'. (Took: 0.72ms) >-
      INFO [02/12/24 11:23:15:84] -< Begin: Finding merge base between 'releases-1.1.0' and 'origin/releases-1.1.0'. >-
        INFO [02/12/24 11:23:15:84] Found merge base of ''83a8f07' - Merge branch 'hotfix/#5181' into 'dev''
        INFO [02/12/24 11:23:15:84] Merge base of 'releases-1.1.0' and 'origin/releases-1.1.0' is ''83a8f07' - Merge branch 'hotfix/#5181' into 'dev''
      INFO [02/12/24 11:23:15:84] -< End: Finding merge base between 'releases-1.1.0' and 'origin/releases-1.1.0'. (Took: 0.53ms) >-
      INFO [02/12/24 11:23:15:85] Multiple source branches have been found, picking the first one (dev).
This may result in incorrect commit counting.
Options were:
dev, origin/dev, main, origin/main
    INFO [02/12/24 11:23:15:85] -< End: Finding branch source of 'releases-1.1.0' (Took: 22.60ms) >-
    INFO [02/12/24 11:23:15:85] -< Begin: Finding merge base between 'origin/hotfix/#5181' and 'dev'. >-
      INFO [02/12/24 11:23:15:85] Found merge base of ''54037dc' - Merge branch 'DEV' into 'main''
      INFO [02/12/24 11:23:15:85] Merge base of 'origin/hotfix/#5181' and 'dev' is ''54037dc' - Merge branch 'DEV' into 'main''
    INFO [02/12/24 11:23:15:85] -< End: Finding merge base between 'origin/hotfix/#5181' and 'dev'. (Took: 0.66ms) >-
    INFO [02/12/24 11:23:15:85] -< Begin: Finding merge base between 'origin/releases-1.1.0' and 'dev'. >-
      INFO [02/12/24 11:23:15:85] Found merge base of ''83a8f07' - Merge branch 'hotfix/#5181' into 'dev''
      INFO [02/12/24 11:23:15:85] Merge base of 'origin/releases-1.1.0' and 'dev' is ''83a8f07' - Merge branch 'hotfix/#5181' into 'dev''
    INFO [02/12/24 11:23:15:85] -< End: Finding merge base between 'origin/releases-1.1.0' and 'dev'. (Took: 0.50ms) >-
    INFO [02/12/24 11:23:15:85] -< Begin: Finding branch source of 'origin/releases-1.1.0' >-
      INFO [02/12/24 11:23:15:86] -< Begin: Finding merge base between 'origin/releases-1.1.0' and 'main'. >-
        INFO [02/12/24 11:23:15:86] Found merge base of ''54037dc' - Merge branch 'DEV' into 'main''
        INFO [02/12/24 11:23:15:86] Merge base of 'origin/releases-1.1.0' and 'main' is ''54037dc' - Merge branch 'DEV' into 'main''
      INFO [02/12/24 11:23:15:86] -< End: Finding merge base between 'origin/releases-1.1.0' and 'main'. (Took: 0.74ms) >-
      INFO [02/12/24 11:23:15:86] -< Begin: Finding merge base between 'origin/releases-1.1.0' and 'releases-1.1.0'. >-
        INFO [02/12/24 11:23:15:86] Found merge base of ''83a8f07' - Merge branch 'hotfix/#5181' into 'dev''
        INFO [02/12/24 11:23:15:86] Merge base of 'origin/releases-1.1.0' and 'releases-1.1.0' is ''83a8f07' - Merge branch 'hotfix/#5181' into 'dev''
      INFO [02/12/24 11:23:15:86] -< End: Finding merge base between 'origin/releases-1.1.0' and 'releases-1.1.0'. (Took: 0.56ms) >-
      INFO [02/12/24 11:23:15:86] -< Begin: Finding merge base between 'origin/releases-1.1.0' and 'origin/dev'. >-
        INFO [02/12/24 11:23:15:86] Found merge base of ''83a8f07' - Merge branch 'hotfix/#5181' into 'dev''
        INFO [02/12/24 11:23:15:86] Merge base of 'origin/releases-1.1.0' and 'origin/dev' is ''83a8f07' - Merge branch 'hotfix/#5181' into 'dev''
      INFO [02/12/24 11:23:15:86] -< End: Finding merge base between 'origin/releases-1.1.0' and 'origin/dev'. (Took: 0.53ms) >-
      INFO [02/12/24 11:23:15:86] -< Begin: Finding merge base between 'origin/releases-1.1.0' and 'origin/main'. >-
        INFO [02/12/24 11:23:15:86] Found merge base of ''54037dc' - Merge branch 'DEV' into 'main''
        INFO [02/12/24 11:23:15:86] Merge base of 'origin/releases-1.1.0' and 'origin/main' is ''54037dc' - Merge branch 'DEV' into 'main''
      INFO [02/12/24 11:23:15:86] -< End: Finding merge base between 'origin/releases-1.1.0' and 'origin/main'. (Took: 0.69ms) >-
      INFO [02/12/24 11:23:15:86] Multiple source branches have been found, picking the first one (dev).
This may result in incorrect commit counting.
Options were:
dev, origin/dev, main, origin/main
    INFO [02/12/24 11:23:15:86] -< End: Finding branch source of 'origin/releases-1.1.0' (Took: 5.64ms) >-
    INFO [02/12/24 11:23:15:86] Release branch exists -> Version in branch name: 1.1.0 with commit source '83a8f07a1ebd287e7c38de7e75bf419d45b821eb'
    INFO [02/12/24 11:23:15:86] Release branch exists -> Version in branch name: 1.1.0 with commit source '83a8f07a1ebd287e7c38de7e75bf419d45b821eb'
  INFO [02/12/24 11:23:15:86] -< End: [Using 'TrackReleaseBranchesVersionStrategy' strategy] (Took: 64.63ms) >-
  INFO [02/12/24 11:23:15:86] -< Begin: [Using 'VersionInBranchNameVersionStrategy' strategy] >-
  INFO [02/12/24 11:23:15:86] -< End: [Using 'VersionInBranchNameVersionStrategy' strategy] (Took: 0.03ms) >-
INFO [02/12/24 11:23:15:86] -< End: Fetching the base versions for version calculation... (Took: 175.61ms) >-
INFO [02/12/24 11:23:15:86] -------------------------------------------------------
INFO [02/12/24 11:23:15:86] Found multiple base versions which will produce the same SemVer (1.2.0-alpha.1), taking oldest source for commit counting (Release branch exists -> Version in branch name)
INFO [02/12/24 11:23:15:86] Base version used: Release branch exists -> Version in branch name: 1.1.0 with commit source '83a8f07a1ebd287e7c38de7e75bf419d45b821eb'
INFO [02/12/24 11:23:15:86] -------------------------------------------------------
INFO [02/12/24 11:23:15:86] -< Begin: Using continuous delivery workflow to calculate the incremented version. >-
  INFO [02/12/24 11:23:15:87] -< Begin: Getting tagged semantic versions from 'refs/heads/dev'.  TagPrefix: [vV]? and Format: Strict >-
    INFO [02/12/24 11:23:15:87] Getting tagged semantic versions. TagPrefix: [vV]? and Format: Strict
  INFO [02/12/24 11:23:15:87] -< End: Getting tagged semantic versions from 'refs/heads/dev'.  TagPrefix: [vV]? and Format: Strict (Took: 6.03ms) >-
  INFO [02/12/24 11:23:15:87] 0 commits found between '83a8f07' - Merge branch 'hotfix/#5181' into 'dev' and '83a8f07' - Merge branch 'hotfix/#5181' into 'dev'
INFO [02/12/24 11:23:15:88] -< End: Using continuous delivery workflow to calculate the incremented version. (Took: 10.83ms) >-
INFO [02/12/24 11:23:15:94] -< Begin: Write version variables to cache file /home/gitlab-runner/builds/DkRhZunrd/0/v4r/dinamo/dinamo-web-api-gateway/.git/gitversion_cache/E247DF9880FCAA66[34](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L34)A517A424D2E6640C8DA[38](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L38)F >-
INFO [02/12/24 11:23:16:00] -< End: Write version variables to cache file /home/gitlab-runner/builds/DkRhZunrd/0/v4r/dinamo/dinamo-web-api-gateway/.git/gitversion_cache/E247DF9880FCAA6634A517A424D2E66[40](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L40)C8DA38F (Took: 64.54ms) >-
Executing GenerateSetVersionMessage for 'GitLabCi'.
1.2.0-alpha.0
Executing GenerateBuildLogOutput for 'GitLabCi'.
GitVersion_Major=1
GitVersion_Minor=2
GitVersion_Patch=0
GitVersion_BuildMetaData=
GitVersion_FullBuildMetaData=Branch.dev.Sha.83a8f07a1ebd287e7c38de7e75bf[41](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L41)9d[45](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L45)b821eb
GitVersion_BranchName=dev
GitVersion_EscapedBranchName=dev
GitVersion_Sha=83a8f07a1ebd287e7c38de7e[75](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L75)bf419d45b[82](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L82)1eb
GitVersion_ShortSha=[83](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L83)a8f07
GitVersion_MajorMinorPatch=1.2.0
GitVersion_SemVer=1.2.0-alpha.0
GitVersion_FullSemVer=1.2.0-alpha.0
GitVersion_AssemblySemVer=1.2.0.0
GitVersion_AssemblySemFileVer=1.2.0.0
GitVersion_PreReleaseTag=alpha.0
GitVersion_PreReleaseTagWithDash=-alpha.0
GitVersion_PreReleaseLabel=alpha
GitVersion_PreReleaseLabelWithDash=-alpha
GitVersion_PreReleaseNumber=0
GitVersion_WeightedPreReleaseNumber=0
GitVersion_InformationalVersion=1.2.0-alpha.0
GitVersion_CommitDate=2024-02-12
GitVersion_VersionSourceSha=83a8f07a1ebd2[87](http://gitlab.dinamoretail.lan/v4r/dinamo/dinamo-web-api-gateway/-/jobs/2661#L87)e7c38de7e75bf419d45b821eb
GitVersion_CommitsSinceVersionSource=0
GitVersion_UncommittedChanges=0
Outputting variables to 'gitversion.properties' ...

[HHobeck]

Hi @DanieleSky. May I ask you: If you take the gitflow workflow. Why would you expect to get the version 1.1.0-beta on develop branch (Or what is your expectation)? The develop branch targets the upcoming minor version of the release branch: 1.2.0-alpha which is correct. Another point is that the label on develop branch is set to alpha. Thus the pre-release tag 1.1.0-beta.1 should be ignored.

Please take a look to the following integration tests to get an understanding how it works:

• GitVersion/src/GitVersion.Core.Tests/IntegrationTests/OtherScenarios.cs

  Line 258 in d878181

  public void EnsurePreReleaseTagLabelWithInitialTagForPatchNumberOneWillBeConsideredIfNoLabelIsDefined()

• GitVersion/src/GitVersion.Core.Tests/IntegrationTests/OtherScenarios.cs

  Line 393 in d878181

  public void EnsurePreReleaseTagLabelWillBeConsideredIfLabelIsEmpty(long patchNumber)

[DanieleSky]

Sorry @HHobeck
I think there is a misunderstanding..
I expect the version 1.1.0-beta because I'm tagging a commit on release branch, not on dev branch...
I think the problem is always this line of log:
INFO [02/12/24 11:23:15:17] Branch from build environment:

Gitversion on GitLab don't know in what branch is when compile a tag.. So it cannot take the right config.
And if the tag's commit is in more than one branch, it took dev because without / or - in he name :|

[HHobeck]

Great you have answered your question by yourself. GitVersion yields to 1.2.0 because it uses the develop branch and not the release branch because the tool cannot decide based on the commit which branch to use. It defaults to the branch without - or / in it.

If you like you can set the environment variable to change the branch:

[DanieleSky]

Thank you @HHobeck for the reply.
The code that are in the screenshot is relative at version 6.0.0-beta.6?
Because I've this version and current branch is always empty (the first highlighted log is the value of CI_COMMIT_REF_NAME)

[HHobeck]

I have no idea what version you are using. The last released version of GitVersion was 6.0.0-beta.5:

• https://github.com/GitTools/GitVersion/releases/

But what I can say this line is very old:

https://github.com/GitTools/GitVersion/blob/support/5.x/src/GitVersion.Core/BuildAgents/GitLabCi.cs#L25

Edit: Can you check which environment variables have been set when running the gitlab pipeline?

[DanieleSky]

Hi HHobeck, sorry for the delay.

Can you check which environment variables have been set when running the gitlab pipeline?

In my screenshot the version printed into the rectangle is relative at this line of code:

So the environment variable is setted.

I forked the project and made some modifies to retrieve correctly the environment variables from Gitlab on linux.
Seems to work, I will open an PR.

[HHobeck]

@DanieleSky I would say this is a bug or at least a new functionality which should be supported by GitVersion. Could you please create an issue with a clear acceptance criteria?

[DanieleSky]

Hi @HHobeck
I've got a question:
It could be reasonable that if GitVersion recognized that the tag commit contains a semantic version (ex. v1.5.0, v1.9.3-beta.1, v2.0.0-rc.1) it will use all the informations / metadata from tag discarding other configurations contained on gitVersion.yaml file?

[HHobeck]

Hi @HHobeck I've got a question: It could be reasonable that if GitVersion recognized that the tag commit contains a semantic version (ex. v1.5.0, v1.9.3-beta.1, v2.0.0-rc.1) it will use all the informations / metadata from tag discarding other configurations contained on gitVersion.yaml file?

Yes that is correct. If the current commit has been tagged, GitVersion uses the semantic version of the tag instead of the next version (when it is compatible with the label of the branch).

[DanieleSky]

ok, great.
But why GitVersion apply others strategies after understand that the commit is a tag commit?
I understand that the tagged commit could be named "my-tagged-commit" so the next version should be calculate from the settings in gitVersion.yaml. But if the tagged commit contains a semantic version no, the gitVersion.yaml shoulded be ignorated.
Do you agree?

[HHobeck]

Actually, I'm not sure if it is in all circumstances necessary. But is it really a problem? As long the correct version will be determined it doesn't matter (except maybe of performance reason). If you have tagged your commit with a pre-release version like 1.0.0-just-a-feature.1, GitVersion needs to know what the branch label is.

Anyway, in the log output it is written that the version calculation is for meta data only. This might be the answer to your question.

[DanieleSky]

For me and my configuration is a problem because in GitLab's pipeline I don't have the name of the branch where the tag is committed. When a pipeline is trigged from tag, the branch name is the name of the tag.
So I don't know if the tag is made in main, dev, release.. I need a gitVersion.yaml configuration only for manage tag, like this:

I think that complicate the tool, forcing me to have a configuration that isn't (in my opinion) necessary.

GitVersion needs to know what the branch label is.

I my opinion only if the tag isn't a "semanting" tag!

To cover the different needs, could be possible to add a configuration's option like Ignore next version if tag contains a semantic version or some like this?

[HHobeck]

For me and my configuration is a problem because in GitLab's pipeline I don't have the name of the branch where the tag is committed. When a pipeline is trigged from tag, the branch name is the name of the tag.
So I don't know if the tag is made in main, dev, release..

Yep I agree that is the problem you are facing.

I need a gitVersion.yaml configuration only for manage tag, [..]
I think that complicate the tool, forcing me to have a configuration that isn't (in my opinion) necessary.

If you see the built-in configuration of GitVersion to fulfill e.g. the gitflow workflow, then you see the configuration is very complex of course. But it is not complex because of the tool, it is complex because of the workflow. What I'm trying to say is: If you find a deficit in the current configuration regarding to the standard supported workflows, then we can address it and change the built-in configuration.

I my opinion only if the tag isn't a "semanting" tag!
To cover the different needs, could be possible to add a configuration's option like Ignore next version if tag contains a semantic version or some like this?

You mean if it is not a pre-release tag right!? I want to state: GitVersion runs always on a branch and takes the configuration based on the information. This is a pre-condition and independent of whether the version strategies are executed or not. For instance in the upcoming version of GitVersion (6.0.0-beta.6) we are using always the next calculated version on develop branch even if the commit has been tagged on main (please see this feature #3453).

Edit:

• [Feature] Same version computed on different branches #3453

[HHobeck]

What would be your expectation if lets say you have two tags on one commit in different branches?

• tag the commit A with v1.0.0-alpha.2 on develop
• merge commit A with fast forward option to main
• tag v1.0.0 on main
• build v1.0.0-alpha.2 in pipeline

[DanieleSky]

for me the result of the pipeline is "v1.0.0-alpha.2" because contains all the informations without the need to calculate the next version

[HHobeck]

Gitversion takes the tag with the highest version. In this example gitversion takes the tag v1.0.0 and not v1.0.0-alpha.2 because he doesn't know which version you have select. GitVersion just sees a commit with two tags.

[DanieleSky]

You mean if it is not a pre-release tag right!? I want to state: GitVersion runs always on a branch and takes the configuration based on the information. This is a pre-condition and independent of whether the version strategies are executed or not. For instance in the upcoming version of GitVersion (6.0.0-beta.6) we are using always the next calculated version on develop branch even if the commit has been tagged on main (please see this feature #3453).

What I want to say is that the branch on which the commit tag is based may not even be known if the tag is semantic. If I tag a version like “v1.0.1” or “v1.0.3-beta.1” that comes from the main, dev, release, or features branch, it doesn’t matter to me because I already have all the informations without the need to calculate the next version. Or am I missing something?

[HHobeck]

[..] If the current commit has been tagged, GitVersion uses the semantic version of the tag instead of the next version (when it is compatible with the label of the branch).

GitVersion runs always on a branch and takes the configuration based on the information. This is a pre-condition and independent of whether the version strategies are executed or not. For instance in the upcoming version of GitVersion (6.0.0-beta.6) we are using always the next calculated version on develop branch even if the commit has been tagged on main (please see this feature #3453).

I think I have answered it multiply times that gitversion needs:

1. a branch to work on
2. a configuration to determine the version based on the branch information (see 1.)

Edit: Obviously what you are trying is not supported by gitversion.

[DanieleSky]

ok @HHobeck
I understand.
I'm not agree about this sentence

[..] If the current commit has been tagged, GitVersion uses the semantic version of the tag instead of the next version (when it is compatible with the label of the branch).

because I've got often a semver different respect of version specified on tag.
But if is only my problem I will search for different solution or using another tool.

[HHobeck]

I'm not agree about this sentence
...
because I've got often a semver different respect of version specified on tag.
But if is only my problem I will search for different solution or using another tool.

If you have such a scenario to always consider the pre-release version independent of the label then you can do it by specifying the label property to null (on root and on branch level). Have you seen and understood the EnsurePreReleaseTagLabelWithInitialTagForPatchNumberOneWillBeConsideredIfNoLabelIsDefined test I have shared previously!?

[DanieleSky]

Hi @HHobeck
I'm returning to you because I'm using the beta.6 from about one month and with this config:

assembly-informational-format: '{SemVer}'
merge-message-formats:
tfs: ''
strategies:
  - ConfiguredNextVersion
  - TaggedCommit
branches:
  hotfix:
    mode: ContinuousDelivery
  tag-beta:
    regex: ^v[0-9]+.[0-9]+.[0-9]+(-beta.[0-9]+)$
    mode: ManualDeployment
    label: 'beta'
    increment: None
    is-release-branch: true

all is working as expected.
The key is the strategies config 😉

thanks for the support

[HHobeck]

Thank you for your feedback. I'm happy that you found a solution for your problem