Azure DevOps basics, it's benefits, comparison with other tools, such as Jenkins, Bamboo etc., sample code!

 What is Azure DevOps?

 

Azure DevOps is a comprehensive suite of development tools and services provided by Microsoft, which  is flexible, platform-agnostic, and cloud-agnostic. This means that you don’t have to use all the services provided by Azure and Azure DevOps for your needs. You can choose the best services according to your requirements without any trouble.

 

Here are its main features:

• Azure Boards: Helps with project management using work items, Kanban boards, and dashboards.

• Azure Repos: Offers version control using Git or Team Foundation Version Control (TFVC).

• Azure Pipelines: Automates building, testing, and deploying applications across various platforms.

• Azure Test Plans: Assists with managing and running manual and automated tests for quality assurance.

• Azure Artifacts: Provides hosting for packages and dependencies, enabling seamless sharing and distribution.

Azure DevOps can integrate with other tools and services, making it versatile for various development workflows. 

Azure DevOps has a wide range of real-world applications across industries.

Here are some examples:

1. Software Development:

   • Automating the build, testing, and deployment process with Azure Pipelines to ensure continuous integration and continuous deployment (CI/CD).

   • Managing source code and version control using Azure Repos, whether for small teams or large enterprises.

2. Cloud Migrations:

   • Managing and tracking the migration process with Azure Boards to ensure smooth planning, task assignments, and progress monitoring.

   • Deploying applications to cloud environments like Azure Kubernetes Service (AKS) through Azure Pipelines.

3. QA and Testing:

   • Running and managing test cases with Azure Test Plans to ensure software quality.

   • Automating performance and stress testing as part of the CI/CD pipeline.

4. Enterprise-Grade Applications:

   • Coordinating large-scale application releases for banks or healthcare providers by integrating DevOps workflows.

   • Managing shared libraries and dependencies using Azure Artifacts.

5. Cross-Platform Mobile Applications:

   • Building and deploying apps for iOS, Android, and Windows platforms using Azure Pipelines.

   • Tracking feature development and bug fixes via Azure Boards.

6. Open-Source Projects:

   • Hosting code repositories in Azure Repos for global collaboration on open-source initiatives.

   • Utilizing Pipelines to ensure code quality and consistency across contributors.

7. IoT Solutions:

   • Automating the deployment of firmware updates to IoT devices.

   • Managing release pipelines for edge computing applications.

Azure DevOps stands out among DevOps tools for its comprehensive suite of services, but its suitability depends on specific needs. Here's a comparison with some popular alternatives:

1. Azure DevOps vs. GitHub:

   • Azure DevOps is ideal for enterprises needing a full suite of DevOps tools, including project management, CI/CD, and testing.

   • GitHub, also owned by Microsoft, is more developer-focused, excelling in open-source collaboration and Git-based workflows.

2. Azure DevOps vs. GitLab:

   • Azure DevOps offers a broader range of services, while GitLab emphasizes an all-in-one platform with strong CI/CD capabilities.

   • GitLab is often preferred for its open-source nature and self-hosting options.

3. Azure DevOps vs. Jenkins:

   • Jenkins is a powerful, open-source CI/CD tool with extensive plugin support, but it requires more manual setup and maintenance.

   • Azure DevOps provides a more integrated and user-friendly experience, especially for teams already using Azure services.

4. Azure DevOps vs. AWS CodePipeline:

   • Azure DevOps integrates seamlessly with Azure cloud services, making it a natural choice for Azure users.

   • AWS CodePipeline is tailored for AWS environments, offering similar CI/CD functionality but with tighter integration into AWS services.

5. Azure DevOps vs. Atlassian Bamboo:

• Bamboo is well-suited for teams using Atlassian tools like Jira and Bitbucket.

• Azure DevOps offers a more comprehensive toolset, including project management and artifact hosting.

Setting up Azure DevOps involves creating an organization, a project, and configuring repositories and pipelines. 

Here's a step-by-step guide:

Step 1: Create an Azure DevOps Organization

1. Sign in to the .

2. Click on "Create new organization."

3. Name your organization and select the region closest to you.

4. Click "Continue" and wait for the organization to be created.

Step 2: Create a Project

1. Within your organization, click "New Project."

2. Name your project and choose its visibility (Private or Public).

3. Click "Create Project."

Step 3: Set Up a Repository

1. Navigate to the "Repos" section.

2. Click the "+" sign to create a new repository.

3. Choose "Git" as the repository type, name it, and optionally add a README file.

Step 4: Configure Azure Pipelines

1. Go to the "Pipelines" section.

2. Click "Create Pipeline" and select your repository.

3. Choose a pipeline template or configure it manually.

4. Save and run the pipeline to automate builds and deployments.

Step 5: Explore Additional Features

• Use Azure Boards for task tracking and project management.

• Set up Azure Test Plans for quality assurance.

• Host packages with Azure Artifacts.

To create a Virtual Network (VNet), a Subnet, and deploy a Virtual Machine (VM) using Azure DevOps, follow these steps:

Step 1: Create the Required ARM Templates

ARM (Azure Resource Manager) templates are JSON files that define your Azure resources. Here's a basic example of the required templates:

vnet-subnet-template.json

{

  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",

  "contentVersion": "1.0.0.0",

  "resources": [

    {

      "type": "Microsoft.Network/virtualNetworks",

      "apiVersion": "2020-11-01",

      "name": "MyVNet",

      "location": "[resourceGroup().location]",

      "properties": {

        "addressSpace": {

          "addressPrefixes": ["10.0.0.0/16"]

        },

        "subnets": [

          {

            "name": "MySubnet",

            "properties": {

              "addressPrefix": "10.0.1.0/24"

            }

          }

        ]

      }

    }

  ]

}

vm-template.json

{

  "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",

  "contentVersion": "1.0.0.0",

  "resources": [

    {

      "type": "Microsoft.Compute/virtualMachines",

      "apiVersion": "2022-03-01",

      "name": "MyVM",

      "location": "[resourceGroup().location]",

      "properties": {

        "hardwareProfile": {

          "vmSize": "Standard_D2s_v3"

        },

        "osProfile": {

          "computerName": "MyVM",

          "adminUsername": "adminUser",

          "adminPassword": "P@ssw0rd123!"

        },

        "networkProfile": {

          "networkInterfaces": [

            {

              "id": "[resourceId('Microsoft.Network/networkInterfaces', 'MyNIC')]"

            }

          ]

        }

      }

    }

  ]

}

Store these templates in your Azure DevOps repository.

Step 2: Configure the Azure DevOps Pipeline

Here's a sample YAML pipeline configuration for deploying the VNet, Subnet, and VM using the templates.

azure-pipelines.yml

trigger:

  - main

pool:

  vmImage: 'ubuntu-latest'

steps:

  # Step 1: Login to Azure

  - task: AzureCLI@2

    displayName: 'Azure Login'

    inputs:

      azureSubscription: '<Your-Service-Connection>'

      scriptType: 'bash'

      scriptLocation: 'inlineScript'

      inlineScript: |

        echo "Logged into Azure successfully."

  # Step 2: Deploy VNet and Subnet

  - task: AzureResourceManagerTemplateDeployment@3

    displayName: 'Deploy VNet and Subnet'

    inputs:

      deploymentScope: 'Resource Group'

      azureResourceManagerConnection: '<Your-Service-Connection>'

      subscriptionId: '<Your-Subscription-ID>'

      resourceGroupName: '<Your-Resource-Group>'

      location: '<Azure-Region>'

      templateLocation: 'Linked artifact'

      csmFile: 'templates/vnet-subnet-template.json'

      deploymentMode: 'Incremental'

  # Step 3: Deploy Virtual Machine

  - task: AzureResourceManagerTemplateDeployment@3

    displayName: 'Deploy Virtual Machine'

    inputs:

      deploymentScope: 'Resource Group'

      azureResourceManagerConnection: '<Your-Service-Connection>'

      subscriptionId: '<Your-Subscription-ID>'

      resourceGroupName: '<Your-Resource-Group>'

      location: '<Azure-Region>'

      templateLocation: 'Linked artifact'

      csmFile: 'templates/vm-template.json'

      deploymentMode: 'Incremental'

Step 3: Execute the Pipeline

1. Commit the azure-pipelines.yml file and templates to your Azure DevOps repository.

2. Navigate to the "Pipelines" section in Azure DevOps and create a new pipeline, pointing it to the YAML file.

3. Run the pipeline and monitor its progress. Once complete, the VNet, Subnet, and VM will be deployed.

Notes:

• Replace placeholders like <Your-Service-Connection>, <Your-Subscription-ID>, <Your-Resource-Group>, and <Azure-Region> with your actual Azure details.

• Ensure the admin password in the VM template meets Azure's complexity requirements.

Below is another sample YAML configuration for an Azure DevOps pipeline that creates a subnet and deploys virtual machines using ARM templates:

trigger:

  - main

pool:

  vmImage: 'ubuntu-latest'

steps:

  # Step 1: Login to Azure

  - task: AzureCLI@2

    displayName: 'Login to Azure'

    inputs:

      azureSubscription: '<Your Service Connection>'

      scriptType: bash

      scriptLocation: inlineScript

      inlineScript: |

        echo "Logging into Azure..."

  

  # Step 2: Deploy ARM Template for Subnet and VM

  - task: AzureResourceManagerTemplateDeployment@3

    displayName: 'Deploy ARM Template'

    inputs:

      deploymentScope: 'Resource Group'

      azureResourceManagerConnection: '<Your Service Connection>'

      subscriptionId: '<Your Subscription ID>'

      resourceGroupName: '<Your Resource Group>'

      location: '<Your Azure Region>'

      templateLocation: 'Linked artifact'

      csmFile: 'templates/deploy.json'

      csmParametersFile: 'templates/deploy.parameters.json'

      overrideParameters: '-subnetName MySubnet -addressPrefix 10.0.1.0/24 -vmName MyVM -vmSize Standard_D2s_v3'

      deploymentMode: 'Incremental'

  # Step 3: Verify Deployment

  - task: AzureCLI@2

    displayName: 'Verify Deployment'

    inputs:

      azureSubscription: '<Your Service Connection>'

      scriptType: bash

      scriptLocation: inlineScript

      inlineScript: |

        echo "Deployment completed successfully!"

Note:

1. Replace <Your Service Connection> with the name of your Azure service connection.

2. Provide values for <Your Subscription ID>, <Your Resource Group>, and <Your Azure Region>.

3. Include your ARM templates (deploy.json and deploy.parameters.json) in your repository. These templates will define the subnet and VM resources.

This pipeline logs into Azure, deploys the ARM template for subnet and VM creation, and verifies the deployment.

Read More