Azure Release Pipelines-DevOps

6 min readJan 26, 2024

A Release Pipeline consumes the Artifacts and conducts follow-up actions within a multi-staging system.

A blue/green deployment is a deployment strategy in which you create two separate, but identical environments. One environment (blue) is running the current application version and one environment (green) is running the new application version.

Using a blue/green deployment strategy increases application availability and reduces deployment risk by simplifying the rollback process if a deployment fails.

Once testing has been completed on the green environment, live application traffic is directed to the green environment and the blue environment is deprecated.

A Build Pipeline is used to generate Artifacts out of Source Code. A Release Pipeline consumes the Artifacts and conducts follow-up actions within a multi-staging system.

Let’s see the release pipeline hands-on 👇

Pipeline → release pipeline → new pipelinev → azure app development

Select s template

Artifactory helps in keeping your data center and automated pipelines ticking, so your business is often running at its best.

Whatever happens, putting in Artifactory with High Availableness ensures that your Artifactory will continue to be available even if one of its nodes is unavailable or down for an upgrade.

One of the foremost benefits of running builds from Artifactory is fully reproducible build.

Click Add an artifact

Click continuous deployment trigger

Continuous deployment triggers allow you to create a release every time a new build artifact is available.

Using the build branch filters you can trigger deployment for a specific target branch. A release will be triggered only if the Git push contains a commit on the specified branch.

The work items represent the core of the Azure DevOps tracking system and can be a bug, a requirement, a general to-do, and so on.

Each work item has a unique ID to keep track of its references from its creation to its implementation as a piece of executable software.

Boards → work items → new work item → task

Go to the queries → Create a new query

Create a chart also

Goto the pipeline click predeployment conditions

Next goto the task

Agent → Modify

Azure Functions deployment slots allow your function app to run different instances called slots. Slots are different environments exposed via a publicly available endpoint.

One app instance is always mapped to the production slot, and you can swap instances assigned to a slot on demand.

Goto the azure portal → webapp → deployment slots → add slot

Staging is a creating different subdomain. its created

Deploy an azure service

Select a path and save

Create a another stage (or) clone & Goto Pre-deployment conditions

Pre-deployment approval name add

Goto the task Check everything is same previous stage. Goto to the pipeline edit

Save to the YAML files

trigger: 
- main

stages:
- stage: Build
  jobs:
  - job: Build
    pool:
      vmImage: 'ubuntu-latest'
    steps:
    - task: Npm@1
      inputs:
        command: 'install'
    - task: Npm@1
      inputs:
        command: 'custom'
        customCommand: 'run build'

    
    - task: PublishBuildArtifacts@1
      inputs:
        PathtoPublish: 'build'
        ArtifactName: 'drop'
        publishLocation: 'Container'