Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Sep 20 22:01
    nikned commented #1812
  • Sep 20 18:00
    maldworth commented #1031
  • Sep 20 08:17
    asbjornu commented #1815
  • Sep 20 07:47
    henrikgjeriksson commented #1815
  • Sep 20 07:45
    henrikgjeriksson commented #1815
  • Sep 20 05:54

    dependabot-preview[bot] on nuget

    (compare)

  • Sep 20 05:54

    arturcic on master

    Bump Microsoft.NET.Test.Sdk fro… (compare)

  • Sep 20 05:54
    arturcic closed #1816
  • Sep 20 05:21
    dependabot-preview[bot] labeled #1816
  • Sep 20 05:21
    dependabot-preview[bot] opened #1816
  • Sep 20 05:21

    dependabot-preview[bot] on nuget

    Bump Microsoft.NET.Test.Sdk fro… (compare)

  • Sep 19 13:42
    underscoreHao commented #1577
  • Sep 19 13:41
    underscoreHao commented #1577
  • Sep 19 13:40
    underscoreHao commented #1577
  • Sep 19 07:32
    kirkone commented #1770
  • Sep 19 06:37
    kirkone commented #1770
  • Sep 19 06:28
    kirkone commented #1770
  • Sep 19 06:25
    arturcic commented #1770
  • Sep 19 06:22
    kirkone commented #1770
  • Sep 19 05:34
    kirkone synchronize #1770
henrik eriksson
@henrik_GJ_Esson_twitter
If you have specified in your yml file to increment minor, then this is the expected behavior. If you specify to increment patch, then instead gitversion will give 2.1.1
GitVersion will calculate the next version for you. This is by design
If you would use GitTag as bearer of version information, the commit which has the actual gittag with version information will dhow that information as version. The following commit(s) will have the calculated next version
Josh Williams
@jackjwilliams
The branch increment strategy is inherit. Since the /diag outputs that it is defaulting to the develop as a source, it's using develops Minor increment I guess.
But why does it keep using develop when I have explicitly said source-branches: ['release'] ?
Geert van Horrik
@GeertvanHorrik
Hi all, I am trying to plan an upgrade to the latest version, and I heavily depend on the dynamic repositories stuff. I am doing a few tests and experience some exceptions. Will try to put the progress here while I work my way through them
Geert van Horrik
@GeertvanHorrik
See GitTools/GitVersion#1758, that should "fix it all"
Artur
@arturcic
Simon Novak
@snovak7
Great news
does this apply also to a Task ?
Its seems yes :) cool
Artur
@arturcic
yes, we include the task as well
Geert van Horrik
@GeertvanHorrik
Party time, well done everyone!
Artur
@arturcic
Yeah, it was a huge release
Thank you everyone for your contribution!
Asbjørn Ulsberg
@asbjornu
@arturcic, fantastic! Great job! 🎉
Artur
@arturcic
Thank you
anaximander23
@anaximander23
quick query regarding the use of GitVersion in builds
specifically, Azure DevOps Pipelines
(using the "classic" editor; I haven't moved this to yaml yet)
I've been using GitVersion on this build for a while and it works great
recently, it seems to have changed how it's tagging the commits when the build is done
it used to come out in the format 2.1.1
now it comes out as 2.1.1+5
how do I get it to stop adding the suffix?
as far as I can tell from the docs, something like $(GitVersion_NuGetVersionV2) should work, but if I use that as the option it prints that as a literal string
and yes, I've added /output buildserver to the additional args
Mattias Karlsson
@devlead
+5 is likely the revision number, each build needs to be unique, tried $(GitVersion.NuGetVersion) mentioned at https://gitversion.readthedocs.io/en/latest/build-server-support/build-server/tfs-build-vnext/
I'm guessing though as I use Cake or MSBuild task myself.
anaximander23
@anaximander23
yeah, I get that it's the build metadata suffix
my point is that it previously wasn't using that in the git tags
and now it is
I want to use the NuGet version for the tag, but it ends up applying the actual string name of the variable, not the value of it
so I suspect that it's not outputting the variables as it should, or something?
Simon Novak
@snovak7
Hello, I have this weird GitVersionTask error
.nuget/packages/gitversiontask/5.0.0/build/GitVersionTask.targets(10,9): error MSB4062: The "WriteVersionInfoToBuildLog" task could not be loaded from the assembly … netstandard2.0/GitVersionTask.MsBuild.dll. Assembly with same name is already loaded Confirm that the <UsingTask> declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
when I build a solution
it works if I build each project separately
Simon Novak
@snovak7
I had more different versions of the same ProjectReference across projects inside Solution… solved
Jakub Suchy
@jakubsuchybio
Hey guys, we are migrating from svn to git and I want to figure out how to version all of our 145+projects. Is there a way to version all of them from just one projects that has GitVersionTask nuget reference? I really don't want to add GitVersionTask to all the projects as it would be total hell.
Let's say the project referencing GitVersionTask is MT.Versioner and every other project references this MT.Versioner. I successfully versioned this MT.Versioner dll. However when I reference MT.Versioner in other projects it doesn't version them. So I tried to read though your docs and found msbuild properties UpdateAssemblyInfo, GenerateAssemblyFileVersionAttribute, GenerateAssemblyInformationalVersionAttribute and GenerateAssemblyVersionAttribute, tried to add them to that MT.Versioner.csproj, but didn't make any difference. Is there a way to do this requirement so that I have only one project referencing nuget GitVersionTask?
Artur
@arturcic
@jakubsuchybio I think you can have a GeneralAssemblyInfo or similar that is referenced in all the projects, and you can set the version for GeneralAssemblyInfo once
Jakub Suchy
@jakubsuchybio
@arturcic Yeah I though about something like that, but don't know how to do that. Because when I create GeneralAssemblyInfo and link it to every other project, then when the GitVersioner versions that file it will be flagged as changed by VCS. So It would need to be partial and make GitVersioner create GeneralAssemblyInfo.Compiled.g which would complete that GeneralAssemblyInfo, but I don't know if linking just GeneralAssemblyInfo.cs would be enought to version other projects :/
henrik eriksson
@henrik_GJ_Esson_twitter
Would you add that GeneralAssemblyInfo to git Ignore? Or have a default one added to the repo, to be able to build without having it generated first?
Recei
Using gitversion 5.0.1. No concerns from our master branch, using trunk based development. But when on a release branch, gitversion fails
2019-09-17 17:23:13 INFO [09/17/19 17:23:13:36] Begin: Finding branch source of 'release/6.0'
2019-09-17 17:23:13 INFO [09/17/19 17:23:13:44] End: Finding branch source of 'release/6.0' (Took: 78.12ms)
2019-09-17 17:23:13 INFO [09/17/19 17:23:13:44] End: Calculating base versions (Took: 3,055.39ms)
2019-09-17 17:23:13 ERROR [09/17/19 17:23:13:49] An unexpected error occurred:
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary2.get_Item(TKey key) at GitVersion.GitRepoMetadataProvider.<>c__DisplayClass15_0.<GetMergeCommitsForBranch>b__0(String sb) at System.Linq.Enumerable.WhereSelectListIterator2.MoveNext()
at System.Linq.Enumerable.AnyTSource
at System.Linq.Enumerable.WhereSelectEnumerableIterator2.MoveNext() at System.Linq.Enumerable.WhereEnumerableIterator1.MoveNext()
at System.Linq.Buffer1..ctor(IEnumerable1 source)
at System.Linq.OrderedEnumerable1.<GetEnumerator>d__1.MoveNext() at System.Collections.Generic.List1..ctor(IEnumerable1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable1 source)
at GitVersion.GitRepoMetadataProvider.GetMergeCommitsForBranch(Branch branch, Branch[] excludedBranches)
at GitVersion.GitRepoMetadataProvider.FindCommitBranchWasBranchedFrom(Branch branch, Branch[] excludedBranches)
at GitVersion.VersionCalculation.BaseVersionCalculators.VersionInBranchNameBaseVersionStrategy.<GetVersions>d1.MoveNext()
at System.Linq.Enumerable.<SelectManyIterator>d
172.MoveNext() at System.Linq.Enumerable.WhereSelectEnumerableIterator2.MoveNext()
at System.Collections.Generic.List1..ctor(IEnumerable1 collection)
at System.Linq.Enumerable.ToListTSource
at GitVersion.VersionCalculation.BaseVersionCalculator.GetBaseVersion(GitVersionContext context)
at GitVersion.VersionCalculation.NextVersionCalculator.FindVersion(GitVersionContext context)
at GitVersion.GitVersionFinder.FindVersion(GitVersionContext context)
at GitVersion.ExecuteCore.<>cDisplayClass7_0.<ExecuteInternal>b0(IRepository repo)
at GitVersion.GitPreparer.WithRepositoryTResult
at GitVersion.ExecuteCore.ExecuteGitVersion(String targetUrl, String dynamicRepositoryLocation, Authentication authentication, String targetBranch, Boolean noFetch, String workingDirectory, String commitId, Config overrideConfig, Boolean noCache)
at GitVersion.SpecifiedArgumentRunner.Run(Arguments arguments, IFileSystem fileSystem)
at GitVersion.Program.VerifyArgumentsAndRun()
2019-09-17 17:23:13 INFO [09/17/19 17:23:13:49]
2019-09-17 17:23:13 INFO [09/17/19 17:23:13:49] Attempting to show the current git graph (please include in issue):
2019-09-17 17:23:13 INFO [09/17/19 17:23:13:49] Showing max of 100 commits
2019-09-17 17:23:14 INFO [09/17/19 17:23:14:08] *
henrik eriksson
@henrik_GJ_Esson_twitter
Is this a known issue? What could the issue be?
henrik eriksson
@henrik_GJ_Esson_twitter
the exception in a more readable format
2019-09-18 15:26:00            INFO [09/18/19 15:26:00:61] Begin: Finding branch source of 'release/6.1'
2019-09-18 15:26:00            INFO [09/18/19 15:26:00:64] End: Finding branch source of 'release/6.1' (Took: 37.90ms)
2019-09-18 15:26:00          INFO [09/18/19 15:26:00:65] End: Calculating base versions (Took: 3,925.10ms)

2019-09-18 15:26:00          ERROR [09/18/19 15:26:00:68] An unexpected error occurred:
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.
   at System.ThrowHelper.ThrowKeyNotFoundException()
   at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
   at GitVersion.GitRepoMetadataProvider.<>c__DisplayClass15_0.<GetMergeCommitsForBranch>b__0(String sb)
   at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
   at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Linq.Enumerable.WhereEnumerableIterator`1.MoveNext()
   at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
   at System.Linq.OrderedEnumerable`1.<GetEnumerator>d__1.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at GitVersion.GitRepoMetadataProvider.GetMergeCommitsForBranch(Branch branch, Branch[] excludedBranches)
   at GitVersion.GitRepoMetadataProvider.FindCommitBranchWasBranchedFrom(Branch branch, Branch[] excludedBranches)
   at GitVersion.VersionCalculation.BaseVersionCalculators.VersionInBranchNameBaseVersionStrategy.<GetVersions>d__1.MoveNext()
   at System.Linq.Enumerable.<SelectManyIterator>d__17`2.MoveNext()
   at System.Linq.Enumerable.WhereSelectEnumerableIterator`2.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at GitVersion.VersionCalculation.BaseVersionCalculator.GetBaseVersion(GitVersionContext context)
   at GitVersion.VersionCalculation.NextVersionCalculator.FindVersion(GitVersionContext context)
   at GitVersion.GitVersionFinder.FindVersion(GitVersionContext context)
   at GitVersion.ExecuteCore.<>c__DisplayClass7_0.<ExecuteInternal>b__0(IRepository repo)
   at GitVersion.GitPreparer.WithRepository[TResult](Func`2 action)
   at GitVersion.ExecuteCore.ExecuteGitVersion(String targetUrl, String dynamicRepositoryLocation, Authentication authentication, String targetBranch, Boolean noFetch, String workingDirectory, String commitId, Config overrideConfig, Boolean noCache)
   at GitVersion.SpecifiedArgumentRunner.Run(Arguments arguments, IFileSystem fileSystem)
   at GitVersion.Program.VerifyArgumentsAndRun()
henrik eriksson
@henrik_GJ_Esson_twitter
Reported issue here: GitTools/GitVersion#1815