Open hansterwal opened 3 months ago
Just had this issue with the azure-pipelines-agent v3.238.0 (which is the latest version per now).
[error]This step requires a node version that does not exist in the agent filesystem. Path: /opt/azure-pipelines-agent/externals/node10/bin/node
The failing task was AWSShellScript@1
, but I assume all tasks will be affected. You'll probably need to add in Node16 like suggested, and update all tasks like you did in #454.
I did some more checking, and for now, node10 is only removed from the "Alternate Agent Downloads" release for 3.238.0 (pipelines-agent, not vsts-agent), so currently it's only affecting users who chose the pipelines agent over the vsts agent to avoid running node6.
@hansterwal @yaunj thanks for bringing this to our attention. I'm taking a look into this + #551. Will update with more details as they come.
Any update on this @rbbarad?
Hi,
First of this is more of a question than a bug.
Our concern is that tasks will start to fail when the support for the node10 runner is dropped as with the node 6 runner prior which was fixed with version 1.1.3.0 . Microsoft released the following call to action last year:
Reference to call to action
Is this something to be worried about?