ChoosingAMachinePool.md

Choosing a Machine Pool

Builds

All Azure Pipelines builds should use the following agent queues

• Pull Request validation and Public CI
  • Windows - dotnet-external-temp
  • Linux - dnceng-linux-external-temp
  • Mac - Hosted macOS
• Official Signed Builds
  • Windows - dotnet-internal-temp
  • Linux - dnceng-linux-internal-temp
  • Mac - Hosted mac Internal

Pools for an Azure DevOps Pipeline can be specified at the build and/or job level in the yaml file (documentation).

Detailed information about the machines in an agent queue can be found in the dotnet-helix-machines repo. Additional dependencies not available on the machines should be bootstrapped in using our Bootstrapping System. If bootstrapping doesn't work for a specific dependency contact @dotnet/dnceng for guidance.

Test Execution

All test execution should run through helix. An up to date list of helix queues can be obtained from the Helix Queue Info Api using the following steps.

• Perform an HTTP GET of https://helix.dot.net/api/2018-03-14/info/queues with your http requesting software of choice. (A web browser works fine)
• You will be presented with a json array containing descriptions of all the queues available in helix.
• All of the queues in the list are available for use in helix. Detailed information about machine setup can be found in the dotnet-helix-machines repo.
• Submit your test jobs to helix using the Helix Sdk.

_{Was this helpful?}