Currently, I have a project in TFS 2013 (using VS 2013) that compiles fine and outputs a .nupkg package file correctly. I receive an error when MSBuild attempts to push that package to our internal ProGet server. Here’s our MSBuild parameters:
Here’s the error from Visual Studio:
(I’ve omitted full paths for brevity and removed the ApiKey)
D:\Builds…\packages\OctoPack.2.0.26\targets\OctoPack.targets (70): The command ““D:\Builds…\packages\OctoPack.2.0.26\targets\NuGet.exe” push “D:\Builds…\OctopusDeploy\obj\octopacked\220.127.116.11.0.nupkg” full-api-key-is-given-here -s https://proget.internalcompany.com/nuget/octopus-dev-feed/Packages” exited with code 1.
Exception Message: MSBuild error 1 has ended this build. You can find more specific information about the cause of this error in above messages. (type BuildProcessTerminateException)
Exception Stack Trace: at System.Activities.Statements.Throw.Execute(CodeActivityContext context)
at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)
at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)
Here’s the error in the TFS log:
OctoPack: OctoPack successful Publish to repository: https://proget.internalcompany.com/nuget/octopus-dev-feed/Packages "D:\Builds\...\Trunk\packages\OctoPack.2.0.26\targets\NuGet.exe" push "D:\Builds\...\OctopusDeploy\obj\octopacked\18.104.22.168.0.nupkg" [api key] -s https://proget.internalcompany.com/nuget/octopus-dev-feed/Packages Pushing 1 22.214.171.124 to 'https://proget.internalcompany.com/nuget/octopus-dev-feed/Packages'... Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
Initially, I discovered that the server that ProGet was running on only allowed 1MB uploads. I’ve since changed that to 10MB and still the same error.
I’m not sure what the TFS log is referring to: “Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.”. This is obviously a systems level problem but what could be causing this? Is TFS 2013 unable to automatically push nuget packages to feeds using the msbuild parameter OctoPackPublishPackageToHttp?