Learn about Job Types in Azure DevOps
Azure DevOps supports different job types in pipelines to enable flexible and efficient CI/CD workflows. Each job type serves a specific purpose, allowing teams to execute tasks in diverse environments and scenarios.
Here's an overview of the job types available.
1. Agent Jobs
Description
Jobs that run on a Microsoft-hosted or self-hosted agent.
Can execute tasks like building code, running tests, deploying artifacts, etc.
Key Features
Executes tasks sequentially on a single agent.
Supports multiple agents for parallel execution (if specified).
Requires defining a pool of agents in the pipeline.
Use Cases
Building and testing applications.
Deploying artifacts to target environments.
Executing tasks requiring pre-installed tools.
2. Server Jobs
Description
Executes tasks directly on the Azure DevOps server, without requiring an agent.
Lightweight and cost-effective as no agent allocation is required.
Key Features
Limited to tasks that can run on the Azure DevOps server (e.g., sending notifications, managing work items).
Cannot execute tasks requiring a specific runtime or build environment.
Use Cases
Administrative tasks like tagging work items or updating pipeline metadata.
Sending notifications or logging specific information.
3. Deployment Jobs
Description
Specialized job type for deploying applications to various environments (e.g., production, staging).
Includes built-in mechanisms for approvals, checks, and deployment strategies.
Key Features
Supports pre- and post-deployment conditions and approvals.
Integrates with environments for tracking and governance.
Can define gates, rollback strategies, and health checks.
Use Cases
Deploying to production or staging environments.
Implementing deployment gates for controlled releases.
Rolling back failed deployments.
4. Container Jobs
Description
Jobs that run inside a container, providing a consistent and isolated environment for tasks.
Key Features
Allows specifying a container image for the job.
Useful for ensuring consistent build/test environments across different stages.
Use Cases
Running tests or builds in a controlled environment.
Ensuring consistent dependencies using Docker images.
Simplifying multi-platform builds.
5. Matrix Jobs
Description
Enables running multiple configurations of a job in parallel with different parameters.
Key Features
Define a matrix of parameters (e.g., OS, versions, environments).
Automatically schedules multiple jobs to execute concurrently based on the matrix.
Use Cases
Running tests across multiple OS platforms or versions.
Building an application for different configurations.
6. Agentless Jobs
Description
Similar to server jobs but runs without any agent or direct server execution.
Often used for external processes.
Key Features
Executes tasks that call external services or APIs.
Lightweight and doesn’t consume agent resources.
Use Cases
Integrating with third-party services or external scripts.
Monitoring or triggering external workflows.
Comparison Table
| Job Type | Runs On | Key Feature | Best Use Case |
|---|---|---|---|
| Agent Job | Agent (hosted/self-hosted) | Sequential/parallel task execution | Building, testing, deploying applications |
| Server Job | Azure DevOps Server | Lightweight, runs without an agent | Administrative tasks, tagging, notifications |
| Deployment Job | Environment or agents | Deployment pipelines with approvals/checks | Deployments with governance and rollbacks |
| Container Job | Containerized agent | Isolated, consistent runtime environments | Builds/tests with Dockerized dependencies |
| Matrix Job | Agent (parallel) | Executes multiple configurations | Multi-platform or version testing |
| Agentless Job | External service/server | Lightweight, external integrations | Triggering/monitoring external workflows |
Choosing the Right Job Type
Development & Testing: Agent jobs or container jobs.
Deployment: Deployment jobs with built-in approval mechanisms.
Multi-Platform Testing: Matrix jobs.
Administrative Tasks: Server or agentless jobs.
Leave a Reply