Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jun 15 2020 13:06
    arturcic unlabeled #2095
  • Jun 15 2020 13:05
    arturcic opened #2328
  • Jun 15 2020 08:09
    github-actions[bot] commented #2122
  • Jun 15 2020 08:09
    github-actions[bot] commented #2300
  • Jun 15 2020 08:09
    github-actions[bot] commented #2306
  • Jun 15 2020 08:09
    github-actions[bot] commented #2310
  • Jun 15 2020 08:09
    github-actions[bot] commented #2311
  • Jun 15 2020 08:09
    github-actions[bot] commented #2320
  • Jun 15 2020 08:09
    github-actions[bot] commented #2327
  • Jun 15 2020 07:49
    arturcic milestoned #2095
  • Jun 15 2020 07:49
    arturcic demilestoned #2095
  • Jun 15 2020 07:46

    arturcic on 5.3.6

    (compare)

  • Jun 15 2020 07:27
    arturcic demilestoned #2241
  • Jun 15 2020 07:27
    arturcic unassigned #2241
  • Jun 15 2020 07:27
    arturcic demilestoned #2074
  • Jun 15 2020 07:26
    arturcic milestoned #2327
  • Jun 15 2020 07:25
    arturcic demilestoned #2318
  • Jun 15 2020 07:25
    arturcic milestoned #2122
  • Jun 15 2020 07:25
    arturcic labeled #2122
  • Jun 15 2020 07:23
    arturcic demilestoned #2313
Dominik Psenner
@dpsenner
Appears I am able to reliably work around this by invoking dotnet publish -maxcpucount:1 .. parallelizing the build breaks GitVersionTask.
Dennis Doomen
@ddoomen_twitter
What if I want to include the metadata number in the number generated for release- branches and take into account the tag. Is this possible?
Dennis Doomen
@ddoomen_twitter
Because I think SemVer 2.0 supports something like 1.2.0-rc.2+34
This message was deleted
Robert Stocks
@stocksr
trying to update my azure devops - which of the 4 packages at https://marketplace.visualstudio.com/publishers/gittools is the current one?
Artur
@arturcic
@stocksr the UseGitversion is the current one, till we get the gittools
package ready
Robert Stocks
@stocksr
image.png
thanks that really helped
Martijn Hoekstra
@martijnhoekstra
How does GitVersion work out when a change is semantically breaking and should increase either major or minor version?
Martijn Hoekstra
@martijnhoekstra
wait, it seems it doesn't
Jesper Melin
@machosallad

Hello there. I'm looking at the examples for GitFlow and at the same time reading the description for Git Branching Strategies for GitFlow. What I cant wrap around my head is the example for Minor Release Branches when combined with the description.

When the branch for release/1.3.0 is created, I figure that the version on branch develop is bumped to 1.4.0 (minor+1) by looking at the version given in the release branch name. A commit is done on the develop branch yielding 1.4.0-alpha.1 (1 = number of commits ahead of release/1.3.0), so far so good. Now to my confusion... Once the release is completed and release/1.3.0 is merged with master and develop I do not understand how the version for develop is determined as 1.4.0-alpha.4? How can develop be 4 commits in front of master at this point since all commits done in release/1.4.0 have been merged both to develop and master?

Brian Garvey
@stonesbg
I need some help. I have setup GitVersion within CakeBuild and have a GitVersion.yml all defined. GitVersion is incrementing the correct number I just can't figure out how it gets pushed back to the repository. Currently it is using the git tag as the baseline so was thinking it was incrementing that but doesn't appear to be the case. The only thing i see is a gitversion.properties. Does this need to be check in in order to get auto increment between builds?
Martijn Hoekstra
@martijnhoekstra
I checked out a tag and try to build a project, I get a warning "It looks like the branch being examined is a detached Head pointing to commit '9dda6ee'. Without a proper branch name GitVersion cannot determine the build version." followed by an error " C:\Program Files\dotnet\sdk\3.1.101\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.GenerateAssemblyInfo.targets(160,5): error MSB4044: The "GetAssemblyVersion" task was not given a value for the required parameter "NuGetVersion". "
I have the impression that's related to the GitVersion plugin
does it ring a bell for anyone?
Martijn Hoekstra
@martijnhoekstra
also, the repo has multiple projects, that I want to version independently of each other. How do I configure that?
Ghost
@ghost~59aef239d73408ce4f7470ac
Guys we are getting this error all of a sudden on Appveyor: ibGit2Sharp.LibGit2SharpException: UsernamePasswordCredentials contains a null Username or Password. We did not change anything. We're using the GITVERSION_REMOTE_USERNAME/PASS env vars.
Any hints?
Aymen Bouchekoua
@NightFox7
Hello Guys. I want to use the overrideconfig argument to set the "mode" option but I got this error Could not parse /overrideconfig option: mode. Currently supported only 'tag-prefix' option Is there another way to do this (other than the GitVersion.yml file of course) ?
Jan Karger ツ ☀
@punker76

Hi, I have a question about getting the major and minor version number from branch names.

Is it possible to parse a branch name for digits? (major.minor)

with such a branch name:

releases/product/release-1-2-2020-branch

So that I get the major.manor = 1.2

Geert van Horrik
@GeertvanHorrik
@punker76 why don't you provide a tag or GitVersionConfig.yaml?

you can either put this in the root (named GitVersionConfig.yaml):

mode: ContinuousDeployment
assembly-versioning-scheme: MajorMinorPatch 
next-version: 1.2.0

OR

tag the branch with 1.2.0

(mostly it's a release branch if you follow GitFlow, so release/1.2.0)
Jan Karger ツ ☀
@punker76
@GeertvanHorrik thx for the tag tipp 🙈 I will try this
Pieter Viljoen
@ptr727
Hi, reasonably new to GitVersion. Using it for a dotnet nuget project from azure devops. Using a master and develop branch. The GitVersion alpha automatically computed version is greater than the master release version, this confuses usage on nuget. How can I get the master version to always be greater than develop alpha of same branch? https://github.com/ptr727/Utilities
Sean Fausett
@gitfool
@arturcic I'd much prefer to depend on a stable release version with the GHA changes :grinning:
... are you still planning to release 5.2.0 soon? :pray:
Sean Fausett
@gitfool
This should also help fix issues with the 5.1.3 version installed on the GHA Windows environments, once it picks it up via Chocolatey.
(https://github.com/actions/virtual-environments/blob/master/images/win/Windows2019-Readme.md#gitversion)
Artur
@arturcic
@gitfool we need to fix GitTools/GitVersion#2131 issue first, then we release 5.2.0
Sean Fausett
@gitfool
@arturcic I can see you're very active today. Thank you so much for your time! It's really appreciated! :cake:
Artur
@arturcic
Thanks, getting close to a version release :-)
Artur
@arturcic
Hi, I'm preparing version 5.2.0 of GitVersion
Artur
@arturcic
GitVersion 5.2.0 was released
Jan Karger ツ ☀
@punker76
@arturcic +1
Gary Ewan Park
@gep13
@arturcic great work!
Mattias Karlsson
@devlead
@arturcic 🎉👍
Sean Fausett
@gitfool
@arturcic :beers:
Sean Fausett
@gitfool
GitVersion 5.2.0 will be in the next GHA virtual envs for Windows 2016/2019
https://github.com/actions/virtual-environments/releases/tag/win19%2F20200308.0
This is important for tools like Cake because unfortunately these globally installed versions currently override the dotnet global tool installed versions
Artur
@arturcic
@gitfool thanks for the link
Pavel Teplukhin
@Dobriy33
Hi, I have a question about commit source finding. GitFlow (default settings of GitVersion).
When we need to merge release/ to develop (via PR) sometimes it needs to resolve conflicts between release and develop. We merge develop to syncronization into release and it breaks commit counting.
       using var fixture = new EmptyRepositoryFixture();
        fixture.Repository.MakeACommit();
        fixture.BranchTo("develop");
        fixture.Repository.MakeCommits(3);
        fixture.AssertFullSemver("0.1.0-alpha.3");
        fixture.BranchTo("release/0.2.0");
        fixture.Repository.MakeACommit();
        fixture.Checkout("develop");
        fixture.Repository.MakeCommits(3);
        fixture.AssertFullSemver("0.3.0-alpha.3");

        // Merge to master
        fixture.Checkout("master");
        fixture.Repository.MergeNoFF("release/0.2.0");

        // Merge to develop
        //first need to sync release with dev to avoid conflict in PR
        fixture.Checkout("release/0.2.0");
        fixture.Repository.MergeNoFF("develop");
        //than merge release to dev
        fixture.Checkout("develop");
        fixture.Repository.MergeNoFF("release/0.2.0");
        fixture.AssertFullSemver("0.3.0-alpha.5"); //but we get alpha.3

        fixture.Repository.MakeACommit();

        fixture.AssertFullSemver("0.3.0-alpha.6");
Mark Woosey
@mrkwse
Has anyone experienced Azure Dev Ops pipelines prefixing the GitVersion environment variables with USEGITVERSION (name of the ADO task)?
e.g. GITVERSION_SEMVER becomes USEGITVERSION_GITVERSION_SEMVER
Mark Woosey
@mrkwse
Looking at GitHub, doesn't look to be a change from GitVersion, and the prefix matching the extension name suggests something may have changed in Azure DevOps, but I can't find any relevant documentation supporting such a change
Felipe
@flipch

Hey guys. My team suddenly started having this issue yesterday where all of our pipelines that used gitversion failed to resolve to any variable.

We had

- task: gittools.gitversion.gitversion-task.GitVersion@4
  displayName: GitVersion
  inputs:
    preferBundledVersion: false

And the build number getting resolved was $(GitVersion.NuGetVersion) instead of the actual formatted version like before yesterday noon PST.

I managed to get the build to populate the variable and build successfully by bumping the version to 5
So now we have

- task: gittools.gitversion.gitversion-task.GitVersion@5
  displayName: GitVersion
  inputs:
    preferBundledVersion: false

Problem is. All of our versions got reset now.

We went from, with @4, 1.5.7 to, with @5, 0.1.0

Can anyone give me a hand in figuring out what to do?

Mark Woosey
@mrkwse
This message was deleted
Felipe
@flipch
What was written?
Mark Woosey
@mrkwse
Sorry I only half read your message and thought it was a different issue
Easiest solution might be to tag your v1.5.7 commit
Felipe
@flipch
I see would that make the subsequent semver's start from there?