Azure DevOps provides YAML pipelines which can apparently only be run in Agent Pools (not Deployment Pools). However, when a job is run, it is only run on one host (agent) in that pool. Since there seems to be no way to create a non-YAML pipeline - how does one deploy to multiple hosts? The scenario here is on-prem agents running on windows servers.
1
votes
AFAIK it is still possible to create non-YAML pipelines? For a release, they are available in the menu under Releases. For builds, you choose the classic editor (last of all options) when creating a new pipeline
– Henry Been
@HenryBeen You are correct. Both types of pipelines are still supported.
– Daniel Mann
When I go this route I still have to choose an Agent Pool and don't get to choose a Deployment Pool. This again means my pipeline runs on only one agent/host and I want to run it on many. Where are deployment pools used anyway??
– Marc
@Marc Deployment pools can be used from a Release, by adding a deployment group job to a release stage. See for example docs.microsoft.com/en-us/azure/devops/pipelines/process/… and docs.microsoft.com/en-us/azure/devops/pipelines/process/…
– Henry Been
The following discussion of the Azure Pipelines muddle is very helpful: github.com/MicrosoftDocs/vsts-docs/issues/4486
– Marc
1 Answers
0
votes
Create a BUILD pipeline w/o using YAML:
Create a RELEASE pipeline:
With a Deployment Group Job:
However none of this helps you if you haven't added your target machines to the Deployment Group
YAML definitions are not yet supported for release pipelines. Multi-stage build pipelines allow the release of code if you're using containers and cloud native apps running on Environment Resources like AKS (kubernetes).