Scribd
Upload
83 views3 pages

Azure DevOps Complete Guide

Uploaded by

onkarlonari71
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
83 views3 pages

Azure DevOps Complete Guide

Uploaded by

onkarlonari71
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Comprehensive Azure DevOps Pipeline Guide

Introduction to Version Control


Version Control allows developers to track and manage changes to code. It enables collaboration by

maintaining a history of every modification.

- **Centralized (SVN)**: A single central repository, where each user checks out and commits

directly to the server.

- **Distributed (Git/GitHub)**: Each user has a full copy of the repository, including history, and

commits locally before pushing to a shared repository (e.g., GitHub).

SVN vs. Azure DevOps


Azure DevOps offers more flexibility than SVN by providing CI/CD pipelines, artifact management,

and environment-specific configurations.

- **SVN Workflow**: Single central repo where all commits are directed.

- **Azure DevOps Workflow**: Allows creating CI/CD pipelines, managing artifacts, and deploying

across different environments.

Understanding Git and GitHub


Git is a version control system for managing source code, while GitHub is a platform for hosting Git

repositories online, supporting collaboration.

Overview of Azure DevOps


Azure DevOps is a suite of tools for CI/CD, version control, project management, and more, aimed

at helping teams deliver high-quality software faster.

Azure DevOps Pipelines


In Azure DevOps, a pipeline automates steps from code integration to deployment.

- **Build Pipeline (CI)**: Compiles, tests, and packages the code to produce an artifact.

- **Release Pipeline (CD)**: Deploys the artifact to different environments (Dev, Test, Production).
Both pipelines can use templates, reducing redundancy and increasing flexibility.

Build Pipeline in Detail


1. **Setup**: Define the build pipeline in YAML, specifying steps like compiling, testing, and

packaging.

2. **Artifacts**: Artifacts produced are environment-agnostic, ensuring consistency across

environments.

Release Pipeline in Detail


1. **Stages**: Separate environments like Dev, Test, and Production with each having unique

configurations.

2. **Gates & Approvals**: Include manual or automated checks before deploying to sensitive

environments.

3. **Variables**: Define environment-specific variables for configurations such as connection strings.

4. **Deployment Groups**: Groups of machines in different environments where the release pipeline

deploys artifacts.

Example Azure DevOps Workflow

Example Workflow:

1. Developer pushes code to the GitHub repository.

2. **Build Pipeline**:

- Triggers automatically on code changes.

- Produces an artifact, stored for future deployments.

3. **Release Pipeline**:

- Defines stages for Dev, Test, and Production environments.

- Applies environment-specific settings and approvals.

4. Deployment Groups target specific machines, ensuring controlled deployment across

environments.
Frequently Asked Questions

Q: What is Azure DevOps?

A: A platform providing CI/CD, project management, and version control tools.

Q: Difference between SVN and Azure DevOps?

A: SVN is centralized, while Azure DevOps is distributed, supports CI/CD, and multiple

environments.

Q: Role of Deployment Groups?

A: Organize target machines per environment for deploying artifacts in the release pipeline.

Q: Stages in Azure DevOps

A: Separates deployment environments with gates, approvals, and environment-specific settings.

You might also like