Today in this article, we will see Azure – Get All Pull requests using ADO DevOps API feature in detail.

It’s easy to call Azure DevOps API and get the pull request details. One can automate the process using the AZ command or CLI or PowerShell script.

We will use the below API for the same.

Trigger an ADO build- using Queue API

GET API

GET https://dev.azure.com/{organization}/{project}/_apis/git/repositories/{repo-name}/pullrequests?&api-version=6.0

Build pipeline With optional parameters

GET API

https://dev.azure.com/jan2022-thecodebuzz/globalexceptionhandler/_apis/git/repositories/globalexceptionhandler/pullrequests?&api-version=6.0

In the above Post request below are the input parameters,

• organization – The name of the Azure DevOps organization.

• project – Project ID or project name

• api version – Version of the API to use.

Below is our sample repository,

https://dev.azure.com/jan2022-thecodebuzz/globalexceptionhandler/_build

Configuration and security

Let’s now configure the API to be invoked securely.

Step1- Click on the User settings and set up the personal access token.

Define a name for this token and authorize the scope of access with this token. You can choose this token access for the Build pipeline trigger or release pipeline trigger etc.

I have below sample 2 pull request

Once you execute the GET API, all metadata associated with Pull request can be accessed easily ,

References:

• Create HTTP with NGINX on Linux in Azure Virtual Machine

• Automating Azure DevOps Build Pipelines using Run Pipeline API

Please bookmark this page and share it with your friends. Please Subscribe to the blog to receive notifications on freshly published (2025) best practices and guidelines for software design and development.

The post Azure – Get All Pull requests using ADO DevOps API first appeared on TheCodeBuzz.

Today in this article, we will see how to use API for automating Azure DevOps ADO Build Pipelines process.

We will see an example of how to trigger Azure Pipelines build via API.

We will look over all 2 approaches to achieve the same,

• Build -Queue API

• Runs – Run Pipeline API

Today in this article, we will cover below aspects,

We will use the below API for the same.

Trigger an ADO build- using Queue API

Calling POST API

POST https://dev.azure.com/{organization}/{project}/_apis/build/builds?api-version=7.1-preview.7

Build pipeline With optional parameters

We can build a pipeline With optional parameters as explained in below example,

Calling POST API

POST https://dev.azure.com/{organization}/{project}/_apis/build/builds?ignoreWarnings={ignoreWarnings}&checkInTicket={checkInTicket}&sourceBuildId={sourceBuildId}&definitionId={definitionId}&api-version=7.1-preview.7

Input Parameters Explained

In the above Post request below are the input parameters,

• organization – The name of the Azure DevOps organization.

• project – Project ID or project name

• api version – Version of the API to use.

Request Body

• definition – The build number/name of the build.

Below is our sample repository,

https://dev.azure.com/jan2022-thecodebuzz/globalexceptionhandler/_build

Configuration and security

Let’s now configure the API to be invoked securely.

Step 1- Click on the User settings and set up the personal access token.

Define a name for this token and authorize the scope of access with this token. You can choose this token access for the Build pipeline trigger or release pipeline trigger etc.

Finally below is our URL and input request object defined,

Define URL

https://dev.azure.com/jan2022-thecodebuzz/globalexceptionhandler/_apis/build/builds?api-version=7.1-preview.7

Let’s now use Postman to execute the API. Please set up the Basic authentication in the Postman by setting up the Token name as UserName and Password as a personal access token.

Below is my request body,

{ 
        "definition": {
            "id": 5
        } 
}

Once you execute the POST API, please check your pipeline. You shall see it is executed and triggered for a build successfully,

References:

• Automating Azure DevOps Build Pipelines using Run Pipeline API

• Create HTTP with NGINX on Linux in Azure Virtual Machine

Do you have any comments or ideas or any better suggestions to share?

Please sound off your comments below.

Happy Coding !!

Please bookmark this page and share it with your friends. Please Subscribe to the blog to receive notifications on freshly published (2025) best practices and guidelines for software design and development.

The post API for automating Azure DevOps ADO Build Pipelines – Part 1 first appeared on TheCodeBuzz.

Today in this article, we will see how to use API for Automating Azure DevOps Build Pipelines using Run Pipeline API.

We will see an example of how to trigger Azure Pipelines build via API. AS we learned in the last article we have below two approaches to call REST API for Build pipeline,

• Build -Queue API
• Runs – Run Pipeline API

We already looked at the Build queue approach in the previous article.

Today in this article, we will cover below aspects,

For more details please see below article,

• API for automating Azure DevOps Build Pipelines – Part 1

Both approaches have similar settings/configuration steps and hence they are easy to configure.

Trigger a build using – Run Pipeline

Build pipeline

POST https://dev.azure.com/{organization}/{project}/_apis/pipelines/{pipelineId}/runs?api-version=6.0-preview.1

Build pipeline With optional parameters

POST API

POST POST https://dev.azure.com/{organization}/{project}/_apis/pipelines/{pipelineId}/runs?pipelineVersion={pipelineVersion}&api-version=6.0-preview.1

Input Parameters

In the above Post request below are the input parameters,

• organization – The name of the Azure DevOps organization.

• project – Project ID or project name

• api version – Version of the API to use.

Request Body

• definition – The build number/name of the build.

Below is our sample repository,

https://dev.azure.com/jan2022-thecodebuzz/globalexceptionhandler/_build

Configuration and security

Let’s now configure the API to be invoked securely.

Step1- Click on the User settings and set up the personal access token.

Define a name for this token and authorize the scope of access with this token. You can choose this token access for Build pipeline trigger or release pipeline trigger etc.

Finally below is our URL and input request object defined,

URL

https://dev.azure.com/jan2022-thecodebuzz/globalexceptionhandler/_apis/pipelines/5/runs?api-version=6.0-preview.1

Let’s now use Postman to execute the API. Please set up the Basic authentication in the Postman by setting up the Token name as UserName and Password as a personal access token.

Request Object for Build Pipeline API

Below is my request body,

{
    "resources": {
        "repositories": {
            "self": {
                "refName": "refs/heads/master"
            }
        }
    }
}

Response from Build Pipeline API

Below is a sample response,

Once you execute the POST API, please check your pipeline. You shall see it is executed and triggered for a build successfully,

References:

• API for automating Azure DevOps Build Pipelines – Part 1

• Create HTTP with NGINX on Linux in Azure Virtual Machine

Do you have any comments or ideas or any better suggestions to share?

Please sound off your comments below.

Happy Coding !!

The post Automating Azure DevOps Build Pipelines using Run Pipeline API first appeared on TheCodeBuzz.

Today in this article, we will cover how to push a container to Azure private registry using Azure CLI.

The Azure Container Registry (ACR) is a private registry that allows you to create, store, and manage container images and related artifacts. The Azure CLI lets you create an Azure container registry instance then, using Docker’s existing widely used commands we can tag and push, pull or run the container image to/from your Azure registry.

In today’s article, we will cover the below aspects,

• Create an Azure cloud resource group
• Create an Azure Container Registry
• Log in to the ACR(Azure Container Registry)
• Use Docker command to Push Image to registry
• Run Image from ACR instance

Prerequisites:

Before getting started, please make sure to install the below prerequisites on your local machine.

• Install Docker – Please see here for instruction
• Install Azure CLI – Please see here for instruction
• Azure Account with a valid subscription

Getting started

Step 1 – Login to Azure cloud subscription account

Please login to the Azure cloud subscription account using Azure CLI,

Command

az login

Step 2 – Create a Resource Groupe

Create a resource group with the az group create command.

This resource will be the logical container to manage all Azure resources.

Command

az group create --name myResourceGroup --location eastus

Example

az group create --name thecodebuzz-group --location eastus

Step 3 – Create an Azure container registry

Command

az acr create --resource-group myResourceGroup
--name myRegistry --sku Basic

Example

az acr create --resource-group thecodebuzz-group --name TheCodeBuzzRegistry --sku basic

Note – Registry name must conform to the following pattern ‘^[a-zA-Z0-9]*$

For More details on the command, please visit this guideline.

Once the registry is created, you will see the below output. Please make a note of the loginServer alone which we will need in the next step,

{
  "adminUserEnabled": false,
  "anonymousPullEnabled": false,
  "creationDate": "2022-02-01T16:48:39.075263+00:00",
  "dataEndpointEnabled": false,
  "dataEndpointHostNames": [],
  "encryption": {
    "keyVaultProperties": null,
    "status": "disabled"
  },
  "id": "/subscriptions/000000000000000/resourceGroups/thecodebuzz-group/providers/Microsoft.ContainerRegistry/registries/TheCodeBuzzRegistry",
  "identity": null,
  "location": "eastus",
  "loginServer": "thecodebuzzregistry.azurecr.io",
  "name": "TheCodeBuzzRegistry",
  "networkRuleBypassOptions": "AzureServices",
  "networkRuleSet": null,
  "policies": {
    "exportPolicy": {
      "status": "enabled"
    },
    "quarantinePolicy": {
      "status": "disabled"
    },
    "retentionPolicy": {
      "days": 7,
      "lastUpdatedTime": "2022-02-01T16:48:40.870939+00:00",
      "status": "disabled"
    },
    "trustPolicy": {
      "status": "disabled",
      "type": "Notary"
    }
  },
  "privateEndpointConnections": [],
  "provisioningState": "Succeeded",
  "publicNetworkAccess": "Enabled",
  "resourceGroup": "thecodebuzz-group",
  "sku": {
    "name": "Basic",
    "tier": "Basic"
  },
  "status": null,
  "systemData": {
    "createdAt": "2022-02-01T16:48:39.075263+00:00",
    "createdBy": "000000000@outlook.com",
    "createdByType": "User",
    "lastModifiedAt": "2022-02-01T16:48:39.075263+00:00",
    "lastModifiedBy": "00000000@outlook.com",
    "lastModifiedByType": "User"
  },
  "tags": {},
  "type": "Microsoft.ContainerRegistry/registries",
  "zoneRedundancy": "Disabled"
}

Step 4 – Log in to the Azure container registry

Let’s now login to the Azure container registry created in the above step,

Command

az acr login --name myRegistry 

Example

 az acr login --name TheCodeBuzzRegistry 

Step 5 – Create Target TAG from Source Tag

This step is required to push an image to an azure registry.

Please use an existing image that you want to push to the Azure registry.

Please visit the below article, on how to create .NET Core application container and push it to DockerHub,

• Build App in a Docker Container – Getting Started

I already have the below docker images locally available

We will be using “thecodebuzzapp” image with TAG as “latest “

Before pushing an image to registry,you must TAG your image with the fully qualified name of your registry login server.

Command

docker tag local-image:tagname <login-server>/new-repo:tagname

Where,

• local-image – Is the name or Id of the local image. In the above example “thecodebuzzapp” is the image name.

• tagname – TAG name used for the local image. In the above example “latest” is the TAG name.

• login-server – Fully qualified login server name for your ACR instance

• new-repo – This is the target/remote repository name where you would like to push the docker local image. This new repository will be your image name as well.

• tagname – TAG name used for target/remote image

Example

docker tag thecodebuzzapp:latest thecodebuzzregistry.azurecr.io/myfirstapp:v1

Above we have created myfirstapp as a repository or placeholder and the same will also be your image name with the V1 as a tag name.

Step 6 – Push the Image to the Azure registry

Finally, let’s use the above target path of the registry to push the image to the Azure ACR instance

Command

docker push <login-server>/new-repo:tag-name

Example

docker push thecodebuzzregistry.azurecr.io/myfirstapp:v1

Verify or List container images from Azure Registry

Please use the below command to list and verify available images in the Azure registry,

Command

az acr repository list --name myRegistryName --output table

Example

az acr repository list --name thecodebuzzregistry --output table

OR

az acr repository list --name thecodebuzzregistry.azurecr.io --output table

You shall see the result below,

The login server endpoint suffix '.azurecr.io' is automatically omitted.

Result

----------
myfirstapp

Run Docker Image from Azure Registry

Now, Let’s run the container image i.e myfirstapp:v1 from our container registry by using the docker run command.

Command

docker run <login-server>/new-repo:tag-name

Example

docker run thecodebuzzregistry.azurecr.io/myfirstapp:v1

And you will see you are running docker Image right from the Azure Registry.

References :

• Docker- Containerize an Angular App with NGNIX

• Build App in a Docker Container – Getting Started

Do you have any comments or ideas or any better suggestions to share?

Please sound off your comments below.

Happy Coding !!

Please bookmark this page and share it with your friends. Please Subscribe to the blog to receive notifications on freshly published (2025) best practices and guidelines for software design and development.

The post Azure CLI – Push a container to Azure Private Registry first appeared on TheCodeBuzz.

Today in this article, we shall see how to Create HTTP with NGINX on Linux in Azure Virtual Machine.

We shall create a Linux Virtual machine with an NGINX webserver and deploy our first application using basic commands and later we will also see how to create an ASP.NET MVC Core application.

Below are the steps we will follow,

Getting started

Sign in to Azure

Sign in to the Azure portal if you haven’t already.

Create a VM on Ubuntu using SSH and HTTP

• On the Virtual machines page, select Create. The Create a virtual machine page opens.

• In the Basics tab, under Project details, please use the correct subscription and then choose to Create a new resource group. Type the name of your choice for the name.*

• Under Instance details,-> for the Virtual machine name -type VM name <vm-name>,

Example

• choose East US as region or region of your choice and
• choose Ubuntu 20.04 LTS for your Image.

• Under Administrator account, select SSH public key as Authentication Type

• In Username* specify the user name of your choice

• For Key pair name

• For SSH public key source, you can leave the default of Generate new key pair.

• For Inbound port rules > Public inbound ports,
  • choose to Allow selected ports and then
  • select SSH (22) and HTTP (80) from the drop-down.

• Select the Review + create 

On the Create a virtual machine page, you get an option to create the Virtual machine.

Download the private key

From the Generate new key pair window,->select Download private key and create the resource.

A private key file will be downloaded to your machine

Example- vmfirst_key.pem

Installing NGINX on Azure Virtual Machine

In previous steps, we created VM successfully. Let’s first connect to VM.

Connect to Virtual Machine

Please go to VM ->Overview-> Connect

Here you will get the Connect option using either SSH or RDP or Bastion

Copy the above command highlighted.

The above commands grab your IP along with the command sample for establishing the connection with the VM.

We will use the above commands in the next step.

Commands copied from above are as below

chmod 400 azureuser.pem

ssh -i azureuser@<Your Public IP for VM>

Using Cloudshell to run SSH commands

Open the Cloudshell CLI command line lets upload the downloaded private key

Please run the below set of commands to connect.

ls

chmod 400 azureuser.pem

ssh -i vmfirst_key.pem azureuser@20.127.10.153

Install NGINX

Please run the below set of commands,

sudo apt-get -y update

sudo apt-get -y install nginx

View Webserver with web application

Once you hit the IP – you shall see a Welcome message from NGINX,

Welcome to nginx!
If you see this page, the nginx web server is successfully installed and working. Further configuration is required.

Let’s add a custom hello message to the Webserver using index.html

azureuser@vmfirst:~$ sudo su

root@vmfirst:/home/azureuser# echo "Hello TheCodeBuzz"> /var/www/html/index.html

Note: Please run the command Sudo su to make you a superuser.

Without Sudo su you will get a Permission denied error.

Setup HTTPS for secured access

As we can see in the screenshot access to our web application is not secure.

To make it secure, we will need to install an SSL certificate and we will enable PORT 443 for Secured access.

I shall cover this in my next article. Until then kindly stay tuned!

Other References:

• Dockerize Angular app with NGINX

Do you have any comments or ideas or any better suggestions to share?

Please sound off your comments below.

Happy Coding !!

Please bookmark this page and share it with your friends. Please Subscribe to the blog to receive notifications on freshly published (2025) best practices and guidelines for software design and development.

The post Create HTTP with NGINX on Linux in Azure Virtual Machine first appeared on TheCodeBuzz.