Learning Key Terminologies in Azure Pipelines

Learning Key Terminologies in Azure Pipelines

Azure Pipelines incorporates various terms and concepts to structure and automate the software delivery lifecycle.

Here’s a detailed overview of these terms.

1. Agent

An Agent is a machine (physical or virtual) that executes the tasks defined in a pipeline.

1. Hosted Agents:

   • Provided by Azure.

   • Pre-configured with common tools and software.

   • Examples: windows-latest, ubuntu-latest.

2. Self-Hosted Agents:

   • Set up and managed by the user.

   • Used for custom configurations or when hosted agents are insufficient.

2. Artifact

An Artifact is a collection of files (e.g., binaries, packages) produced during a build or pipeline execution.

1. Purpose:

   • Artifacts are used as inputs for subsequent stages (e.g., deployment).

   • Examples: Compiled code, Docker images, configuration files.

2. Storage: Stored in Azure Artifacts, a container registry, or external storage.

3. Build

A Build is the process of compiling, packaging, and assembling source code into executable or deployable artifacts.

1. Steps:

   • Compile source code.

   • Resolve dependencies.

   • Run unit tests.

2. Output: Generates build artifacts such as .exe, .dll, or .jar files.

4. Continuous Delivery (CD)

Continuous Delivery (CD) ensures that software is always in a deployable state and can be released to production at any time.

Key Features:

• Automates deployment to staging and production environments.

• Integrates approval workflows to control releases.

• Supports deployment strategies like blue-green and canary.

5. Continuous Integration (CI)

Continuous Integration (CI) automates the process of integrating code changes into a shared repository frequently.

Key Steps:

• Triggered by code commits or pull requests.

• Builds the code and runs tests automatically.

• Provides rapid feedback on integration issues.

6. Deployment Target

A Deployment Target is the environment or infrastructure where the application is deployed.

Examples:

• Virtual Machines.

• Azure App Service.

• Kubernetes Clusters.

• On-premises servers.

7. Job

A Job is a collection of tasks that run sequentially on the same agent.

Characteristics:

• Each job has its own execution context.

• Multiple jobs can run in parallel if supported by the pipeline.

8. Pipeline

A Pipeline is the overall workflow that defines the processes of building, testing, and deploying applications.

Types:

• Build Pipeline: Focuses on compiling and testing code.

• Release Pipeline: Handles deployment to various environments.

Definition:

YAML file (azure-pipelines.yml) or graphical user interface (classic pipelines).

9. Release

A Release represents a specific version of an application ready for deployment.

Components:

• Includes build artifacts.

• Maps to environments (e.g., Dev, QA, Production).

• Can have pre- or post-deployment approvals.

10. Stage

A Stage is a logical grouping of jobs within a pipeline, often corresponding to a specific environment.

Examples:

• Development stage.

• Testing stage.

• Production stage.

Benefits:

• Simplifies pipeline organization.

• Supports sequential or parallel execution.

11. Task

A Task is a single, specific step within a job.

Examples:

• Compiling code.

• Running tests.

• Deploying artifacts.

Customization:

Use built-in tasks or define custom tasks in the pipeline.

12. Trigger

A Trigger defines the conditions that initiate a pipeline or job.

Types of Triggers:

1. Continuous Integration Trigger: Starts the pipeline when code changes are pushed to a repository.

2. Pull Request Trigger: Executes the pipeline when a pull request is created or updated.

3. Scheduled Trigger: Runs the pipeline at a specified time (e.g., nightly builds).

4. Manual Trigger: Allows users to start a pipeline manually.

Summary

Understanding these terms provides a solid foundation for working with Azure Pipelines and managing CI/CD workflows effectively.