Azure-pipelines-agent: How can the version of Node.js be updated in the build agent? I have a module that requires 6.X or higher and 5.x ships with the agent.
I have a custom build task with a node module that requires 6.x or higher of node, however the agent ships with a 5.x version. I attempted to install node 7.x on the agent, including the path to point to 7.x but the agent still uses 5.x. Any suggestions?
mjwoodsphx
All 8 comments
agent will start use node 6.10.3 from next version release. i will target next week to 2.117.0 agent.
TingluoHuang
on 19 May 2017
Note that means your task will have to demand a minimum agent version of 2.117.0. That means if your task is used, it will trigger an update of any 2.x agent.
bryanmacfarlane
on 19 May 2017
bryanmacfarlane
on 19 May 2017
Will the new agent be compatible with either TFS 2017 or 2017 update 1?
mjwoodsphx
on 19 May 2017
yes, it should.
TingluoHuang
on 19 May 2017
2.117.1 agent is available for this - it's rolling through the hosted pools now finishing up tomorrow. you can download if needed. it has node 6 LTS
bryanmacfarlane
on 2 Jun 2017
The agent is way behind, were on node v9.0 now and its using 6.11, please update asap
IAMtheIAM
on 20 Dec 2017
you can use the nodejs tool installer to specify a version of node to use in your builds. heres a link to the docs https://docs.microsoft.com/en-us/vsts/build-release/tasks/tool/node-js
chazguerrero
on 23 Jan 2018
Related issues
alexrainman
路
5Comments
moorichardmoo
路
5Comments
muthurathinam
路
3Comments
simonvane
路
3Comments
gitfool
路
4Comments
Most helpful comment
The agent is way behind, were on node v9.0 now and its using 6.11, please update asap