Integrate DevTest Labs environments into Azure Pipelines
You can use the Azure DevTest Labs Tasks extension to integrate Azure DevTest Labs into Azure Pipelines. In this article, you use the extension to create and deploy an environment, and then delete the environment, all in one pipeline. You can use the environment to integrate your Azure Pipelines continuous integration/continuous delivery (CI/CD) release pipelines with Azure DevTest Labs.
The Azure DevTest Labs Tasks extension adds the following tasks to Azure Pipelines:
- Create an Environment
- Delete an Environment
These tasks make it easy to quickly deploy an environment for a specific test, and then delete the environment when you finish the test. You'd ordinarily do the environment creation and deletion separately in your own pipelines.
For information about other extension tasks like creating VMs and custom images, see Integrate DevTest Labs into Azure Pipelines.
- In the Azure portal, create a DevTest Labs lab, or use an existing lab. Make sure your lab is configured to use Public Environment, which is turned on by default.
- Register or sign into your Azure DevOps Services organization, and create a project, or use an existing project.
- Install the Azure DevTest Labs Tasks extension from Visual Studio Marketplace into your Azure DevOps Services organization.
Create a release pipeline and environment
In your Azure DevOps project, select Releases under the Pipelines section.
Select New pipeline.
Select a template on the right shows a list of templates for common deployment patterns. Select the Empty job link at the top of the page.
On the New release pipeline page, drop down Tasks in the toolbar and select Stage 1.
Select the plus sign + next to Agent job.
Under Add tasks, search for and select Azure DevTest Labs Create Environment, and then select Add.
On the left, select the Azure DevTest Labs Create Environment task.
Fill out the Azure DevTest Labs Create Environment (Preview) form as follows:
Azure RM Subscription: Select your connection or Azure subscription from the dropdown list.
For information about creating a more restricted permissions connection to your Azure subscription, see Azure Resource Manager service endpoint.
Lab: Select the lab name you want to deploy against. You can also use a variable,
$(labName). Manually entering the name causes failure. Select the name from the dropdown list.
Environment Name: Enter the name of the environment to create in the lab.
Repository: Select the source code repository that contains the template.
You can choose the default repository, Public Environment Repo, or another repository that contains the template you want to use. Repositories are designated in the lab policies. Manually entering the friendly name causes failures. Select the name from the dropdown list.
Template: Select the template to use to create the environment. Manually entering the friendly name cause failures. Select the name from the dropdown list.
Parameters File: Browse to the location of a saved parameters file.
Parameter Overrides: Pass custom parameters to the environment.
You can use either Parameters File, Parameter Overrides, or both to set parameter values. For example, you can use these fields to pass the encrypted password. You can also use variables to avoid passing secret information in the logs, and even connect to Azure Key Vault.
Delete the environment
The final pipeline stage is to delete the environment that you deployed. You'd ordinarily delete the environment after doing the developer tasks or running the tests on the deployed resources.
In the release pipeline, select the plus sign + next to Agent job.
In the Add tasks window, search for and add Azure DevTest Labs Delete Environment.
On the left, select the Azure DevTest Labs Delete Environment task.
Fill out the form as follows:
- Azure RM Subscription: Select your connection or subscription.
- Lab: Select the lab where the environment exists.
- Environment Name: Select the name of the environment to delete.
Select New release pipeline at the top of the release pipeline page, and enter a new name for the pipeline.
Select Save at upper right.
Submit and view feedback for