azure-devops-docs | official Azure DevOps documentation for Microsoft | Azure library

Ok, I think I have it sorted out now and the pipeline stages are running successfully. It was a combination of adding DOCKER_BUILDKIT: 1 like:

How will I use the docker save command in Azure pipeline task after docker build. The available docker task doesn't have this command.

This related to the task version.

Steps: Add task docker->switch the task version to 0->select the option Run a Docker command, then we could run the docker save command, check the pic below.

Is there any better way of doing this apart from saving an image.

We recommend that you use this to upload the docker image as an artifact.

You can use the REST API instead of Azure CLI to get the information. It can be used with the standard tools already present on the Microsoft Hosted agents. It requires only vanilla powershell or powershell core, meaning to works on both windows and linux agents. The below example was successfully tested on windows-latest/windows-2019 and ubuntu-latest/ubuntu-20.04

The approach is the same as with Azure CLI.

1. List all available groups filtered by name to retrieve the variable group in question
2. Get all variables in the variable group using the variable group id from step

In fact, the pipeline also has an out of the box PAT token available with read access to variable groups. It is stored in the variable System.AccessToken. Using that instead of a manually managed one will further simplify things.

The script below is executed in a pwsh step, which is the built in Powershell task in Powershell core mode

You can try to create a new incognito window and sign in to your organization : https://dev.azure.com/{organizationName} with the invited account in this incognito window.

This is because when the user clicked the email invitation, this will automatically jump to the browser to use the default account cached by the browser to log in to the organization, and this default account could not be the invited account.

Per the latest docs, there is indeed a trick, which is to put a blank line after the HTML element to allow nested markdown, and otherwise use a

AzureDevops Deployment Group won't run on Windows Server 2019

According to the error message: