Azure DevOps Build Templates

Collection of useful templates for Azure DevOps YAML pipelines. This repository provides reusable pipeline templates that standardize common build and deployment tasks in Azure DevOps.

Description	Status
Quality Gate
Bugs
Code Smells
Maintainability Rating
Security Rating
CodeQL

Table of Contents

• Overview
• Available Templates
• Quick Start
• Documentation
• Contributing

Overview

These templates are designed to be reusable across multiple projects and provide standardized patterns for:

• Running Azure CLI commands with different script types
• Deploying Bicep templates across different Azure scopes
• Building and pushing Docker images
• Running acceptance tests with .NET support
• Managing template repository resources

Available Templates

Template	Purpose	Documentation
azure-cli.yml	Execute Azure CLI commands	View Details
bicep-deploy.yml	Deploy Azure Bicep templates	View Details
docker.yml	Build and push Docker images	View Details
run-acceptance-tests.yml	Run acceptance tests	View Details
use-template-files.yml	Checkout template repository	View Details

Quick Start

1. Required Repository Setup

⚠️ REQUIRED: All templates require the repository to be referenced as almguru-templates. Add this to your pipeline's resources section:

resources:
  repositories:
  - repository: almguru-templates
    type: github
    name: almguru/build-templates
    endpoint: MyGitHubServiceConnection
    ref: main

2. Basic Usage Example

# azure-pipelines.yml
trigger:
- main

resources:
  repositories:
  - repository: almguru-templates
    type: github
    name: almguru/build-templates
    endpoint: MyGitHubServiceConnection
    ref: main

stages:
- stage: Deploy
  jobs:
  - job: DeployInfrastructure
    steps:
    - template: pipelines/lib/bicep-deploy.yml@almguru-templates
      parameters:
        azureSubscription: 'my-azure-connection'
        deploymentScope: 'ResourceGroup'
        resourceGroupName: 'my-resource-group'
        file: 'infrastructure/main.bicep'

Documentation

📖 Complete Template Documentation - Detailed documentation with parameters, examples, and usage patterns for all templates.

Contributing

We welcome contributions to improve these templates! Please follow our guidelines:

Branch Naming Convention

This repository follows a structured branch naming convention. All branches must use one of these prefixes:

• features/ - For new features or enhancements
• bugfix/ - For bug fixes
• hotfix/ - For urgent production fixes
• docs/ - For documentation updates
• chore/ - For maintenance and cleanup tasks

Examples:

• features/add-docker-template
• bugfix/fix-bicep-parameter-parsing
• docs/update-readme

📖 Complete Branch Naming Guide - Detailed information about our branch naming conventions.

How to Contribute

1. Fork the repository
2. Create a feature branch following our naming convention: git checkout -b features/your-feature-name
3. Make your changes
4. Test the templates in your pipeline
5. Submit a pull request

Our automated checks will verify that your branch follows the naming convention.

For questions or issues, please create an issue in this repository.