What happened?
I try to use agent without node6, node10 from alternate agent downloads, e.g. https://download.agent.dev.azure.com/agent/4.273.0/pipelines-agent-linux-x64-4.273.0.tar.gz
When I installed this agent and ran in --once mode for container usage, I saw a long time - 40s or more then 1m for the Initializing job task.
I thought it was because of downloading tasks for job, but no, tasks downloads take 5s — just one, two simple tasks.
The reason is that this type of pipeline agent - without node6 task runner detects the missing node6 runner and downloads a huge node6 runner package from somewhere in Microsoft cloud and installs it into /azp/externals.
Why?
This pipeline agent - from pipelines-agent-* package - is intentionally without old node6 runner. So downloading this deprecated runner back is a problem, especially in --once mode, when the agent is clean for each job. Agent checks for this deprecated runner and eventually downloads this huge node6 package before every job.
I don't need old runner either, my jobs have mostly only docker@2, bash@3 task. I use slimer distribution agent package intentionally, because I don't need old task runners at all.
with standard distribution package - e.g. https://download.agent.dev.azure.com/agent/4.273.0/vsts-agent-linux-x64-4.273.0.tar.gz - it's ok, because these agents has bundled old runner in the package.
Plese remove the check and download old node6 runner before starting first job.
Versions
4.273.0 - from https://download.agent.dev.azure.com/agent/4.273.0/pipelines-agent-linux-x64-4.273.0.tar.gz - Linux
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu 24.04
Version controll system
Git
Relevant log output
What happened?
I try to use agent without node6, node10 from alternate agent downloads, e.g. https://download.agent.dev.azure.com/agent/4.273.0/pipelines-agent-linux-x64-4.273.0.tar.gz
When I installed this agent and ran in
--oncemode for container usage, I saw a long time - 40s or more then 1m for theInitializing jobtask.I thought it was because of downloading tasks for job, but no, tasks downloads take 5s — just one, two simple tasks.
The reason is that this type of pipeline agent -
without node6 task runnerdetects the missing node6 runner and downloads a huge node6 runner package from somewhere in Microsoft cloud and installs it into/azp/externals.Why?
This pipeline agent - from
pipelines-agent-*package - is intentionally without old node6 runner. So downloading this deprecated runner back is a problem, especially in--oncemode, when the agent is clean for each job. Agent checks for this deprecated runner and eventually downloads this huge node6 package before every job.I don't need old runner either, my jobs have mostly only docker@2, bash@3 task. I use slimer distribution agent package intentionally, because I don't need old task runners at all.
with standard distribution package - e.g. https://download.agent.dev.azure.com/agent/4.273.0/vsts-agent-linux-x64-4.273.0.tar.gz - it's ok, because these agents has bundled old runner in the package.
Plese remove the check and download old node6 runner before starting first job.
Versions
4.273.0 - from https://download.agent.dev.azure.com/agent/4.273.0/pipelines-agent-linux-x64-4.273.0.tar.gz - Linux
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu 24.04
Version controll system
Git
Relevant log output