| ms.topic | include |
|---|---|
| ms.service | azure-devops-pipelines |
| ms.author | sdanie |
| ms.manager | mijacobs |
| author | steved0x |
| ms.date | 02/12/2020 |
-
Go to the Agent pools tab:
[!INCLUDE agent-pools-tab]
-
Select the pool that contains the agent.
-
Make sure the agent is enabled.
-
Go to the capabilities tab:
[!INCLUDE agent-capabilities]
-
Look for the
Agent.Versioncapability. You can compare this value against the latest published agent version on the Azure Pipelines Agent page. -
Each agent automatically updates itself when it runs a task that requires a newer version of the agent. If you want to manually update some agents, right-click the pool, and then select Update all agents.
::: moniker range="< azure-devops"
Yes. Beginning with Azure DevOps Server 2019, you can configure your server to look for agent package files on a local disk. This configuration overrides the default version that came with the server at the time of its release. This scenario also applies when the server doesn't have access to the internet.
-
From a computer with internet access, download the latest version of the agent package files (in .zip or .tar.gz form) from the Azure Pipelines Agent GitHub Releases page.
-
Transfer the downloaded package files to each Azure DevOps Server Application Tier by using a method of your choice (for example, USB drive, network transfer, and so on). Place the agent files under the
%ProgramData%\Microsoft\Azure DevOps\Agentsfolder. If there's no folder labeled Agents, create one. -
You're all set! Your Azure DevOps Server now uses the local files whenever the agents are updated. Each agent automatically updates itself when it runs a task that requires a newer version of the agent. But if you want to manually update some agents, right-click the pool, and then choose Update all agents.
::: moniker-end