ערוך

שתף באמצעות

Quickstart: Create a Managed DevOps Pool using the Azure portal

  • מאמר

Important

Managed DevOps Pools is currently in PREVIEW. See the Supplemental Terms of Use for Microsoft Azure Previews for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.

This article shows you how to create a Managed DevOps pool, and run a pipeline in the new pool.

Prerequisites

Before completing the steps in this article, you must configure your Azure subscription and Azure DevOps organization for use with Managed DevOps Pools, as described in the Prerequisites article. These steps need to be completed only once per Azure subscription and Azure DevOps organization.

Create the Managed DevOps Pools resource

  1. Sign in to the Azure portal.

  2. Search for Managed DevOps Pools and select it from the available options.

  3. Choose Create, or Create Managed DevOps Pools if this is your first pool.

    Screenshot of Create Managed DevOps Pools button.

  4. Specify the Subscription, Resource group, Dev Center, and Dev Center project. If you haven't yet created a resource group, Dev Center, or Dev Center project, you can create them in this step. Screenshot of Create Managed DevOps Pools initial configuration settings.

  5. Specify the Azure DevOps organization you want to use with your pool, the name of the pool, and the region for your pool.

    Screenshot of Azure DevOps organization field.

    By default pools are configured for all projects in a single organization. You can configure additional organizations or limit the projects on the Security tab. Choose a region that is close to the other Azure resources you're using for best cost and performance.

  6. Specify the maximum number of agents you wish to be available (Maximum agents), the virtual machine size of the agents (Agent size), and the OS disk type for the agents. D2adsV5 is the default Agent size; choose Change size to pick a different size if desired.

    Screenshot of agent size, count, and OS disk type.

    Agent sizes (SKUs) with available Managed DevOps Pools quotas are marked as Available. You can request more quota for Not Available SKUs. Once a quota request for a Not Available SKU is approved, it will then be listed as Available. Learn more about Managed DevOps Pools quotas.

  7. Configure the images for your pool. By default pools are created with a single image. To change the image or configure multiple images, choose Add from Image Library and select the image or images you want to use for your pool.

    Screenshot if Images section.

  8. Configure any desired additional settings for your pool by choosing the corresponding tab. View each tab to see the default settings for Managed DevOps Pools, and see the following links for more information about the settings available on each tab. To use the default settings for the following sections, continue to Review + create.

    Screenshot of tabs of settings.

    • Scaling - Configure scaling settings to manage the performance and cost of your Managed DevOps Pool. The default setting is stateless agents with no standby agents.
    • Networking - Add agents from your Managed DevOps Pool to your virtual network. The default setting is an isolated virtual network for your agents.
    • Storage - Attach an empty data disk to your agents. The default is no attached data disk.
    • Security - Configure organization and project access, specify pool permissions, and configure interactive mode for testing. The default is a pool configured for all projects in the organization specified in Azure DevOps organization.
    • Tags - Use tags to organize your Azure resources and management hierarchy.

  9. Choose Review + create, and choose Create to confirm.

    Screenshot of Review + create for Managed DevOps Pools initial configuration settings.

    The provisioning process can take a few moments. When the agent pool creation is complete, you can view the pool in Azure DevOps and run pipelines in that pool.

    If your subscription doesn't have the capacity to configure your pool with the desired Azure VM SKU and maximum agents count, pool creation fails with an error similar to the following message. Cores needed to complete this request is 8, which exceeds the current limit of 0 for SKU family standardDDSv4Family in region eastus. Please choose a different region if possible, or request additional quota at https://portal.azure.com/#view/Microsoft_Azure_Support/NewSupportRequestV3Blade/issueType/quota/subscriptionId/subscription_id_placeholder/topicId/3eadc5d3-b59a-3658-d8c6-9c729ba35b97. To resolve the issue, see Review Managed DevOps quotas.

View the agent pool in Azure DevOps

  1. Go to the Azure DevOps portal and sign in to your Azure DevOps organization (https://dev.azure.com/{your-organization}).

  2. Go to Azure DevOps > Organization settings.

    Screenshot of Organization settings button.

  3. Go to Pipelines > Agent pools, and verify that your new pool is listed. If you just created the Managed DevOps Pool, it can take a few moments for the new pool to appear in the agents list.

    Screenshot of Agent pools list.

Run a pipeline in your new pool

In this step, we'll create a simple pipeline in the default repository of an Azure DevOps project and run it in your new Managed DevOps Pool.

  1. Go to the Azure DevOps portal and sign in to your Azure DevOps organization (https://dev.azure.com/{your-organization}).

  2. Go to the project where you want to run the pipeline, and choose Pipelines.

    Screenshot of Projects list.

  3. Choose New pipeline (or Create Pipeline if this is your first pipeline).

    Screenshot of new pipeline button.

  4. Choose Azure Repos Git.

    Screenshot of repository types.

  5. Choose the repository that has the same name as your project. In this example, the project is named FabrikamFiber, so we choose the repository with the same name.

    Screenshot of FabrikamFiber repository.

  6. Choose Starter pipeline.

    Screenshot of pipeline template list.

  7. By default the starter template uses a Microsoft hosted Linux agent. Edit the pipeline template and change the pool section so that it refers to the pool you created in the previous steps.

    # Change these two lines as shown in the following example.
 pool:
  vmImage: ubuntu-latest

    In this example, the Managed DevOps Pools is named fabrikam-managed-pool, so replace vmImage: ubuntu-latest with name: fabrikam-managed-pools, and specify the name of your Managed DevOps Pool.

    # Replace fabrikam-managed-pools with the name
# of your Managed DevOps Pool.
pool:
  name: fabrikam-managed-pool

  8. Choose Save and run, and choose Save and run a second time to confirm.

    Screenshot of save and run button.

  9. If this is the first pipeline run in this pool, you may be asked to grant permissions before the pipeline runs.

  10. Watch the pipeline run in Azure DevOps, and you can switch over to the Azure portal and see the running agent in the Agents view.