You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/build-server-support/build-server/azure-devops
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ See [MSBuild Task](/usage/msbuild-task) for further instructions how to use the
14
14
3. Set the Tool parameter to `<pathToGitVersion>\GitVersion.exe`.
15
15
4. Set the Arguments parameter to `/output buildserver /nofetch`.
16
16
5. If you want the GitVersionTask to update AssemblyInfo files add `updateAssemblyInfo true` to the Arguments parameter.
17
-
6. If you want to update the build number you need to send a [logging command](https://github.com/Microsoft/vsts-tasks/blob/master/docs/authoring/commands.md) to TFS.
17
+
6. If you want to update the build number you need to send a [logging command](https://github.com/Microsoft/azure-pipelines-tasks/blob/master/docs/authoring/commands.md) to TFS.
18
18
19
19
### Using the custom GitVersion build step
20
20
#### Installing
@@ -68,6 +68,6 @@ Just checking the `Clean Repository` check box in the build definition settings
68
68
You can force deletion of the whole folder and a re-clone containing all tags by settings the variable `Build.Clean` to `all`.
69
69
This will take more time during build but makes sure that all tags are fetched.
70
70
In the future it is planned to allow using `git.exe` instead of current `libgit2sharp` for syncing the repos which might allow other possibilities to solve this issue.
71
-
For details see this [GitHub issue](https://github.com/Microsoft/vsts-tasks/issues/1218).
71
+
For details see this [GitHub issue](https://github.com/Microsoft/azure-pipelines-tasks/issues/1218).
72
72
* If running a build for a certain commit (through passing the commit SHA while queueing the build) all tags from the repository will be fetched, even the ones newer than the commit.
73
73
This can lead to different version numbers while re-running historical builds.
0 commit comments