Open trevorNgo opened 6 years ago
I have also attempted to run a script with a user credential, but to no avail.
I'm sorry, I don't have an Azure environment to experiment in anymore. The key is making sure there are elevated administrative permissions. I believe (but am not 100% certain) there are flags you can pass in Powershell to accomplish this.
I recently added a validating installation section to the wiki that describes how the install should look... perhaps that will help with troubleshooting? Aside from that, the only other issues are mirrors and permissions.
I wish I could be of more help, but I just don't have the environment to assess the issue.
I'd probably utilize a custom build agent for this. See https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-windows?view=azure-devops
Do we have any solution to this? I want to achieve the same. Any help will be appreciated.
Hi there,
I am trying to use Azure Devops Pipeline to switch installed node package versions on our build machine. Running a very basic script "nvm use 6.10.0" in a powershell/command line script, I get the successful "using 6.10.0" message, however when checking nvm list on the build machine, it is still using version 10.10.0 (highlighted in the screenshot).
It appears only manual nvm use script works, I am not sure of the internal workings of nvm on windows but will it be possible to change node package in the Azure pipeline?
Thanks in advance,
Script: nvm use 6.10.0 nvm list