This document discusses strategies for implementing builds in Azure Pipelines. It outlines the options of using Microsoft-hosted agents or self-hosted agents. Microsoft-hosted agents handle maintenance and upgrades, provide a fresh virtual machine for each run, and discard the VM after use. Self-hosted agents can be installed on Linux, macOS, or Windows machines, or Docker containers. Azure Pipelines also allows running parallel jobs on Microsoft-hosted or self-hosted infrastructure, with Microsoft providing a free tier that includes at least one parallel job. The document also briefly discusses capabilities that can be automatically discovered or user-defined.

1. Implementing a Build Strategy

2. HELLO!
I am Eng Teong Cheah
Microsoft MVP for AI
You can find me at @walkercet
2

3. Azure Pipelines agents
3

4. Microsoft-
hosted
agents
▸ Maintenance and upgrades
are taken care of for you.
▸ Each time you run a pipeline,
you get a fresh virtual
machine.
▸ The virtual machine is
discarded after one use.
▸ Can run jobs directly on the
VM or in a container
4

5. Self-hosted
agents
▸ You can install the agent on
Linux, macOS, or Windows
machine. You can also
install an agent on a Docker
container.
5

6. Parallel jobs
▸ In Azure Pipelines, you can
run parallel jobs on
Microsoft-hosted
infrastructure or on your own
(self-hosted) infrastructure.
▸ Microsoft provides a free tier
of service by default in very
organization that includes at
least one paralle job.
6

7. Capabilities
▸ Capabilities are name-value
pairs that are either
automatically discovered by
agent software, in which
case they are called system
capabilities, or those that
you define, in which case
they are called user
capabilities.
7

8. Demo
Creating a Jenkins Build Job and Triggering CI
- Wrapping Jenkins Job within Azure Pipelines
8

15. 9 THANKS!
Any questions?
You can find me at
▸ @walkercet

16. Resources
Microsoft Docs
10