Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Teamcity nuget not working after 2017.1 upgrade

Sebastian Claesson Hoffback April 21, 2017

Directly after the Teamcity 2017.1 upgrade we can no longer use nuget in our build steps. We get the error: 'C:\Program' is not recognized as an internal or external command

Has anyone else experienced this? I We are using nuget 3.4.4 and i also tried 4.1.0 and it gave me the same error.

Full error:

[Step 1/9] install: Installing NuGet packages for Asimov.API\packages.config
[17:08:03][install] NuGet command: "C:\Program Files\TeamCity\buildAgent\plugins\nuget-agent\bin\JetBrains.TeamCity.NuGetRunner.exe" "C:\Program Files\TeamCity\buildAgent\work\5a90d8f68a293a75\.nuget\NuGet.exe" install "C:\Program Files\TeamCity\buildAgent\work\5a90d8f68a293a75\Asimov.API\packages.config" -OutputDirectory "C:\Program Files\TeamCity\buildAgent\work\5a90d8f68a293a75\packages"
[17:08:03][install] Launching ""C:\Program Files\TeamCity\buildAgent\plugins\nuget-agent\bin\JetBrains.TeamCity.NuGetRunner.exe"" in working directory C:\Program Files\TeamCity\buildAgent\work\5a90d8f68a293a75\Asimov.API as it is not present in checkout directory C:\Program Files\TeamCity\buildAgent\work\5a90d8f68a293a75
[17:08:03][install] Running interpreter: C:\Windows\system32\cmd.exe
[17:08:03][install] Passing user provided executable and arguments to interpreter as a single string (will not split arguments): "C:\Program Files\TeamCity\buildAgent\plugins\nuget-agent\bin\JetBrains.TeamCity.NuGetRunner.exe" "C:\Program Files\TeamCity\buildAgent\work\5a90d8f68a293a75\.nuget\NuGet.exe" install "C:\Program Files\TeamCity\buildAgent\work\5a90d8f68a293a75\Asimov.API\packages.config" -OutputDirectory "C:\Program Files\TeamCity\buildAgent\work\5a90d8f68a293a75\packages"
[17:08:03][install] Starting: C:\Windows\system32\cmd.exe /s /c "C:\Program Files\TeamCity\buildAgent\plugins\nuget-agent\bin\JetBrains.TeamCity.NuGetRunner.exe" "C:\Program Files\TeamCity\buildAgent\work\5a90d8f68a293a75\.nuget\NuGet.exe" install "C:\Program Files\TeamCity\buildAgent\work\5a90d8f68a293a75\Asimov.API\packages.config" -OutputDirectory "C:\Program Files\TeamCity\buildAgent\work\5a90d8f68a293a75\packages"
[17:08:03][install] in directory: C:\Program Files\TeamCity\buildAgent\work\5a90d8f68a293a75\Asimov.API
[17:08:03][install] 'C:\Program' is not recognized as an internal or external command,
[17:08:03][install] operable program or batch file.
[17:08:03][install] Process exited with code 1
[17:08:03][install] Process exited with code 1
[17:08:03][Step 1/9] Step Install from NuGet (NuGet Installer) failed

2 answers

1 accepted

0 votes
Answer accepted
Sebastian Claesson Hoffback April 23, 2017

I now tried the following.

 

1.

On a clean install of windows Server 2016 I installed TeamCity into c:\Program Files\TeamCity

The build failed with the same error

2.

I then uninstalled and tried again with the installation path c:\TeamCity

And it worked!

So I guess that I will nog have to reinstall in my real server with a path witout spaces. Will file a bugreport since this sould work in any folder

0 votes
Sebastian Claesson Hoffback April 23, 2017

Someone beat me to it. Bug report here: 

https://youtrack.jetbrains.com/issue/TW-49789

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events