ops-cli | cli wrapper Terraform , Ansible , Helmfile and SSH | Infrastructure Automation library

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

pipelineId is equal to definitionId

So please go to your pipeline and check url like this https://dev.azure.com/thecodemanual/DevOps%20Manual/_build?definitionId=177.

Or use this endpoint to get list of deifnitions:

The documentation does not contain explnaition of your issue, but you can try this example with rest API through PowerShell:

No, you don't need az devops login. What you need is Azure CLI Task:

And if it is ok, how can I create and finish a PR request in build pipeline?

The easiest way would be to use Create Pull Request Task with "Set Auto Complete" option checked.

If you want to do it from CLI, generate PAT Token:

Save it as secret variable:

An use powershell to save it as env variable

Firstly, please make sure you can access the Azure DevOps organization (https://dev.azure.com/{organization}) from the bastion host. Otherwise we cannot connect to the Azure DevOps services.

Secondly, please check if you are running a firewall or a proxy on the bastion host. If you're running an agent in a secure network behind a firewall, make sure the agent can initiate communication with the URLs and IP addresses mentioned in below documents.

• What URLs does the agent need to communicate with?

• How do I configure the agent to bypass a web proxy and connect to Azure Pipelines?

Working Solution

Because all of my builds are centralised in one pipeline template, I changed this template to trigger my pipeline A on successful publishing of an artifact. Here's the pipeline trigger code which is pretty much verbatim from (https://docs.microsoft.com/en-us/azure/devops/cli/azure-devops-cli-in-yaml?view=azure-devops), apart from the last couple of steps:

As a prerequisite,your Azure CLI version must be 2.0.49 at a minimum. You can use az --version to validate.

After you add az extension, you could also run az login to sign in.

If you have already signed in with az login interactively or using user name and password, then you don't have to provide a token as az devops commands now support sign in through az login.

When you are using az devops login command, first make sure you are using Azure DevOps Service organization URL. Example: https://dev.azure.com/MyOrganizationName. Azure DevOps Server/TFS is not support at present.

For Azure DevOps tokens, you need to make sure it's valid and with enough scopes for this token to authorize for your specific tasks.

More details please refer our official tutorial here-- Sign in with a Personal Access Token (PAT)