Open ashtonian opened 8 years ago
We have the exact same issue now. Fortunately we can disable that agent and use others, but it should be fixed anyway.
We experience the same issue after installing nvm-windows on our build servers into C:\Program Files\nvm
. Would be great to get an fix for that issue in the future! :)
[20:01:24]Step 1/7: Set Node Version 8.9.4 (Node.js NVM Installer) (2s)
[20:01:24]Download: Fetching NVM (1s)
[20:01:24]Downloading creatonix/nvm...
[20:01:24]from https://github.com/creationix/nvm/archive/v0.7.0.zip
[20:01:26]NVM downloaded into C:\BuildAgent\system\jonnyzzz.nvm
[20:01:26]Install: Installing Node.js v8.9.4
[20:01:26]Starting: D:\TCBuildAgent\temp\agentTmp\custom_script6116987364866104114.cmd
[20:01:26]in directory: C:\BuildAgent\system\jonnyzzz.nvm
[20:01:27]Version 8.9.4 is already installed.
[20:01:27]Process exited with code 0
[20:01:27]Use: Selecting Node.js v8.9.4
[20:01:27]Starting: D:\TCBuildAgent\temp\agentTmp\custom_script914166534282904116.cmd
[20:01:27]in directory: C:\BuildAgent\system\jonnyzzz.nvm
[20:01:27]exit status 1: 'C:\Program' is not recognized as an internal or external command,
[20:01:27]operable program or batch file.
[20:01:27]
[20:01:27]Process exited with code 0
I believe I'm having a problem with spaces in the build agent's directory path for the gulp runner. The output is as following: