Quick Notes168 words
Complex pipeline scenarios — quick notes
Complex scenarios — quick notes
| Fact | Detail |
|---|---|
| Hybrid control connection | Agent/runner connects outbound; no internet-initiated inbound port is needed for that service connection |
| On-prem deployment target | Self-hosted agent inside the network |
| VM resources in an environment | Deployment history per machine; unlocks rolling |
rolling constraint | VM resources only |
| Elastic self-hosted | VMSS runs in your Azure subscription; Managed DevOps Pools uses Microsoft-managed infrastructure and is recommended |
| VM image/template choice | VMSS: Marketplace/custom; Managed Pools: Azure Pipelines, Marketplace, or Compute Gallery, with multiple images supported |
| Reproducibility on self-hosted | Container jobs pin OS/tools/dependencies and reduce host-toolchain drift; shared host state still needs hygiene |
| Job dependencies for a run | Service containers |
Traps
- The service control connection is outbound, but the agent still needs network access to each private target.
- Containers reduce host-toolchain drift; they do not clean every shared-host cache, configuration, or workspace.