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: README.md
+26
Original file line number
Diff line number
Diff line change
@@ -207,6 +207,32 @@ the project called `GitFlowVersion.NugetVersion`. If many of your projects uses
207
207
can add the parameter to the "root-project" (TeamCity 8.x+)
208
208
* Then setup you nuget pack build set the "version" to `%GitFlowVersion.NugetVersion%`
209
209
210
+
### When TeamCity -> GitHub can't use https
211
+
GitFlowVersion requires the presence of master branch in order to determine the version number. If TeamCity uses https to clone git repos then GitFlowVersion will pull down master branch for you during the build.
212
+
213
+
If however your TeamCity uses SSH to clone git repos and https is unavailable then GitFlowVersion will error with a message like
214
+
> [GitFlowVersionTask.UpdateAssemblyInfo] Error occurred: GitFlowVersion.MissingBranchException: Could not fetch from '[email protected]:Xero/Bus.git' since LibGit2 does not support the transport. You have most likely cloned using SSH. If there is a remote branch named 'master' then fetch it manually, otherwise please create a local branch named 'master'. ---> LibGit2Sharp.LibGit2SharpException: An error was raised by libgit2. Category = Net (Error).
215
+
This transport isn't implemented. Sorry
216
+
217
+
You need to create a TeamCity build step before your compile step which manually creates a local master branch which tracks remote master. Like so (in powershell):
218
+
219
+
```Powershell
220
+
$branchBeingBuilt = . git symbolic-ref --short -q HEAD
0 commit comments