Learn more.Īll of these machines have at least 10 GB of free disk space available for your pipelines to run. If data sovereignty is important to you and if your organization is not in the US, then you should not use macOS images. These agents always run in the US irrespective of the location of your Azure DevOps organization. These virtual machines are co-located in the same geography as your Azure DevOps organization.Īgents that run macOS images are provisioned on Mac pros with a 3 core CPU, 14 GB of RAM, and 14 GB of SSD disk space. Microsoft-hosted agents that run Windows and Linux images are provisioned on Azure general purpose virtual machines with a 2 core CPU, 7 GB of RAM, and 14 GB of SSD disk space. Layout of the hosted agents is subject to change without warning. Hard-code the drive letter or folder that contains the repository. To refer to the build environment and agent resources. When you use a Microsoft-hosted agent, always use variables If you notice that your pipeline is not running on the expected image, make sure that you verify the pool specification at all levels. The specification of a pool can be done at multiple levels in a classic build pipeline - for the whole pipeline, or for each job. When using macOS images, you can manually select from tool versions.
Freespace source code project software#
You can see the installed software for each hosted agent by choosing the Included Software link in the table. For more information, see Designate a pool in your pipeline. The default agent image for classic build pipelines is windows-2019, and the default agent image for YAML build pipelines is ubuntu-latest. Windows Server 2019 with Visual Studio 2019 Windows Server 2022 with Visual Studio 2022
The Azure Pipelines agent pool offers several virtual machine images to choose from, each including a broad range of tools and software. You can try a Microsoft-hosted agent for no charge.
0 kommentar(er)
