Επεξεργασία

Κοινή χρήση μέσω

Download assets by using Azure Pipelines

  • Άρθρο

You can automate the download of assets from the Asset library in Microsoft Dynamics Lifecycle Services (LCS) by using the Dynamics Lifecycle Services (LCS) Asset Download task in Azure DevOps.

This article assumes that you have a working knowledge of Azure Pipelines.

Note

Before you can add these steps to a pipeline, the Dynamics 365 finance and operations Tools extension for Azure DevOps must be enabled and installed in the Azure DevOps account. For more information about how to install an extension for an organization, see Install extensions.

Make sure that MSAL.PS is installed

Versions 1.* and later of the download task require availability of the MSAL.PS PowerShell library. A task is available to automatically install the tools during pipeline execution. This task can be added anywhere in the stage before the download task. For more information, see Add the MSAL.PS install task to a pipeline.

Add the task to a pipeline

To add the task to the build of your YML or Classic pipeline, search the task list for Dynamics Lifecycle Services (LCS) Asset Download.

The following table describes the options that are available for this task.

Input name Mandatory Description
LCS Connection Yes Select or create a service connection to LCS. For more information, see Create an LCS connection in Azure Pipelines.
LCS Project ID Yes Enter the ID of the project in LCS that contains both the asset to deploy and the target environment. You can find the project ID at the end of the URL of your project's dashboard.
Path to download to Yes Enter the path to download the asset to.
Search Pattern Yes Select the type of search pattern that should be used to find the asset in the Asset library in LCS. Depending on the value that you select, the following options are available:
  • Asset ID (guid) – If you select this value, in the LCS File Asset Id(s) field, enter the asset ID or a semicolon-separated list of asset IDs. Asset IDs are globally unique identifiers (GUIDs).
  • Name – If you select this value, in the LCS File Asset Type field, select the asset type. Then, in the LCS File Asset Name field, specify the name to search for. You can use an asterisk (*) as a wildcard character in the name. For example, you might enter MyPackage*.

After a successful download, an output variable can be used to capture a list of the file paths. If there are multiple files, a semicolon-separated list of file paths is assigned to the output variable. For more information about output variables in Azure DevOps, see Use output variables from tasks.