Skip to main content

What is Azure DevOps Extension in Azure CLI and How to install?

 


Azure DevOps Extension in Azure CLI expands the capabilities of the Azure CLI to interact with Azure DevOps services. It provides commands for managing work items, pipelines, repositories, test plans, and other DevOps resources directly from the command line.

Here are the general steps to install the Azure DevOps CLI extension:

Prerequisites:

1.       > Azure CLI:

Make sure you have the Azure CLI installed on your machine. You can download it from the official Azure CLI website: https://learn.microsoft.com/en-us/cli/azure/install-azure-cli

Steps to Install Azure DevOps CLI Extension:

1. Open a Command Prompt or Terminal:

           Open your command-line interface. This could be a Command Prompt on Windows, a Terminal on macOS/Linux, or Azure Cloud Shell.

      2. Install the Azure DevOps Extension:

            Run the following command to install the Azure DevOps CLI extension:

                    az extension add --name azure-devops

       3. Sign Into Azure DevOps:

     Once installed, sign in to your Azure DevOps organization using:

              az devops login

    This will open a browser window to authenticate.

4. Verify Installation:

           To verify that the extension is installed, you can run:

                   az extension list

            Look for "azure-devops" in the list of installed extensions.

Using the Azure DevOps CLI Extension:

After installation, you can use the Azure DevOps CLI commands to interact with your Azure DevOps resources. For example, you can use commands like az pipelines, az boards, az repos, etc., to manage pipelines, work items, and repositories. Here are a couple of examples:

# List all projects in the organization

az devops project list

# Show information about a specific project

az devops project show --id <project-id>

# List all work items in a project:

az boards work-item query --project <MyProject>

Benefits:

  • Flexibility: Manage DevOps resources from the command line, even without a GUI.
  • Efficiency: Perform actions quickly and efficiently with direct commands.
  • Scripting and Automation: Automate DevOps tasks and integrate them into CI/CD pipelines.

 

 

Labels:

Comments

Post a Comment

Popular posts from this blog

How to Unzip files in Selenium (Java)?

1) Using Java (Lengthy way) : Create a utility and use it:>> import java.io.BufferedOutputStream; import org.openqa.selenium.io.Zip; import java.io.File; import java.io.FileInputStream; import java.io.FileOutputStream; import java.io.IOException; import java.util.zip.ZipEntry; import java.util.zip.ZipInputStream;   public class UnzipUtil {     private static final int BUFFER_SIZE = 4096;     public void unzip (String zipFilePath, String destDirectory) throws IOException {         File destDir = new File(destDirectory);         if (!destDir.exists()) {             destDir.mkdir();         }         ZipInputStream zipIn = new ZipInputStream(new FileInputStream(zipFilePath));         ZipEntry entry = zipIn.getNextEntry();         // to iterates over entries in the zip folder         while (en...
Post a Comment
Read more

The use of Verbose attribute in testNG or POM.xml (maven-surefire-plugin)

At times, we see some weird behavior in your testNG execution and feel that the information displayed is insufficient and would like to see more details. At other times, the output on the console is too verbose and we may want to only see the errors. This is where a verbose attribute can help you- it is used to define the amount of logging to be performed on the console. The verbosity level is 0 to 10, where 10 is most detailed. Once you set it to 10, you'll see that console output will contain information regarding the tests, methods, and listeners, etc. <suite name="Suite" thread-count="5" verbose="10"> Note* You can specify -1 and this will put TestNG in debug mode. The default level is 0. Alternatively, you can set the verbose level through attribute in "maven-surefire-plugin" in pom.xml, as shown in the image. #testNG #automationTesting #verbose # #testAutomation
Post a Comment
Read more

Encode/Decode the variable/response using Postman itself

We get a lot of use cases where we may have to implement Base64 encoding and/or decoding while building our APIs. And, if you are wondering if it is possible to encode/decode the variable/response using Postman itself or how to encode/decode the token or password in postman and save it in a variable? To Base64 encode/decode, the quickest way is to use JavaScript methods btoa, atob: atob - It turns base64-encoded ASCII data back to binary. btoa - It turns binary data to base64-encoded ASCII. Sample code : var responseBody = pm.response.json(); var parsedPwd = JSON.parse(atob(responseBody.password)); // presuming password is in the payload pm.collectionVariables.set("password", parsedPwd);
Post a Comment
Read more