How to Create a Pipeline in Azure DevOps Using YAML
How do you create a pipeline in Azure DevOps using YAML? You create a pipeline in Azure DevOps using YAML by defining a pipeline configuration file (azure-pipelines.yml) in your code repository, which describes the build and deployment steps, enabling automation, version control, and repeatable CI/CD workflows within your DevOps process.
For enterprise executives, using YAML pipelines ensures standardized delivery practices, improves auditability, and integrates seamlessly with infrastructure-as-code strategies across engineering teams.
Step 1: Prerequisites and Access
Before creating a YAML pipeline, ensure you have:
- An Azure DevOps organization and project
- A Git repository (Azure Repos, GitHub, or Bitbucket) connected to the project
- Contributor access to the repo and pipeline permissions
Tip: Ensure repository permissions are scoped correctly to prevent unauthorized pipeline changes.
Step 2: Create the YAML File in Your Repository
The core of a YAML-based pipeline is the azure-pipelines.yml file located in the root directory of your codebase.
Example: Basic YAML Pipeline
trigger:
– main
pool:
vmImage: ‘ubuntu-latest’
steps:
– task: NodeTool@0
inputs:
versionSpec: ’18.x’
displayName: ‘Install Node.js’
– script: |
npm install
npm run build
displayName: ‘Install dependencies and build’
This pipeline:
- Runs when code is pushed to the main branch
- Uses a Microsoft-hosted Ubuntu runner
- Installs Node.js, then installs dependencies and builds the project
Best Practice: Keep the YAML file in version control to track pipeline changes alongside application code.
Step 3: Connect Your Repo and Configure the Pipeline
- Go to Azure DevOps Pipelines
- Click New Pipeline
- Choose your repository source (Azure Repos, GitHub, etc.)
- Select YAML as the configuration type
- Azure DevOps will auto-detect azure-pipelines.yml if it exists in the repo
Once detected:
- Review the preview
- Click Run to trigger your first build
Executive Insight: YAML pipelines increase developer autonomy and reduce reliance on manual pipeline configuration via UI.
Step 4: Add Stages, Jobs, and Deployment Environments
For more advanced scenarios, break your pipeline into stages and jobs for deployment orchestration.
Example: Multi-Stage Pipeline
trigger:
– main
stages:
– stage: Build
jobs:
– job: BuildJob
pool:
vmImage: ‘ubuntu-latest’
steps:
– script: echo “Building…”
– stage: Deploy
dependsOn: Build
condition: succeeded()
jobs:
– job: DeployJob
pool:
vmImage: ‘ubuntu-latest’
steps:
– script: echo “Deploying to production…”
This pipeline includes separate Build and Deploy stages with conditional logic and job isolation.
Pro Tip: Use stage approvals and environment gates for secure deployments in enterprise environments.
Step 5: Use Templates and Variables for Reusability
Keep pipelines DRY (Don’t Repeat Yourself) by modularizing them into reusable templates.
Example: Template Usage
# azure-pipelines.yml
trigger:
– main
extends:
template: templates/build-and-test.yml
Also use pipeline variables to customize behavior:
variables:
node_version: ’18.x’
Scalability Tip: Reusable templates are ideal for managing pipelines across microservices or multi-team projects.
Step 6: Monitor, Debug, and Secure Your Pipeline
Once your pipeline runs:
- Review logs and results in the Pipelines > Runs section
- Use Logs and Timeline views to debug issues
- Implement secure file handling, variable groups, and secrets via Azure Key Vault integration
Security Insight: Limit YAML editing to trusted contributors and enforce branch protection rules for pipeline-triggering branches.
Final Thoughts
Creating a pipeline in Azure DevOps using YAML empowers development teams to define CI/CD workflows as code, ensuring consistency, versioning, and automation at scale. For enterprise organizations, YAML pipelines are a foundational tool in DevOps transformation and cloud-native delivery.
