gitversion

How to make the Gitversion VSTS increment release number on master?

由 元气小坏坏 提交于 2021-01-03 05:34:27
问题 I have configured my git repository in VSTS with the GitFlow repository. I have a master branch with a dotnet core project, and a release branch called 'Release/1.0.0'. When I create a pull-request and merge the release/1.0.0 branch back to master, it does not increment it's version number to 1.0.0. Instead, it's increasing the version number from 0.1.0 (the base fallback) to 0.1.1. Build log: Calculating base versions Fallback base version: 0.1.0 with commit count source xx Git tag '0.1.0':

How to make the Gitversion VSTS increment release number on master?

由 你说的曾经没有我的故事 提交于 2021-01-03 05:34:16
问题 I have configured my git repository in VSTS with the GitFlow repository. I have a master branch with a dotnet core project, and a release branch called 'Release/1.0.0'. When I create a pull-request and merge the release/1.0.0 branch back to master, it does not increment it's version number to 1.0.0. Instead, it's increasing the version number from 0.1.0 (the base fallback) to 0.1.1. Build log: Calculating base versions Fallback base version: 0.1.0 with commit count source xx Git tag '0.1.0':

Setting Git Tag from Azure Devops Build Pipeline on Complete

由 青春壹個敷衍的年華 提交于 2020-04-30 06:37:07
问题 I'm trying to set a tag with the current version number determined by GitVersion on the GIT commit at the end of a successful build. Feels like I can't be the first one to be doing this, but I'm struggling to find something that works. Azure Devops Pipeline has a feature in Get Soources to "Tag sources" On Success. I've set this and set to a variable that is set by one of the Agent Tasks I have (GitVersion) I can see in the debug logs that this variable is getting set by the GitVersion

Label Sources with $(GitVersion.NuGetVersion) creates Tag with variable name, not value

由 情到浓时终转凉″ 提交于 2019-12-06 06:03:55
问题 After a successful build, having configured the Label Format as $(GitVersion.NuGetVersion) , the resulting tag is set to $(GitVersion.NuGetVersion) not the actual expanded value of that variable. In the build output logging, there are 2 sections/plans: Build, and Finalize Build. Presumably, all the variable context/state is being lost once the build agent moves to the second section/plan. How am I supposed to tag the source with the resulting GitVersion if the context of the GitVersion

Label Sources with $(GitVersion.NuGetVersion) creates Tag with variable name, not value

由 佐手、 提交于 2019-12-04 11:16:03
After a successful build, having configured the Label Format as $(GitVersion.NuGetVersion) , the resulting tag is set to $(GitVersion.NuGetVersion) not the actual expanded value of that variable. In the build output logging, there are 2 sections/plans: Build, and Finalize Build. Presumably, all the variable context/state is being lost once the build agent moves to the second section/plan. How am I supposed to tag the source with the resulting GitVersion if the context of the GitVersion variables are lost during the Finalize Build section? https://github.com/Microsoft/vsts-agent/issues/716 I
订阅 gitversion