What is the difference between Individual CI and Batched CI in Azure Pipelines ?
How does it relate to the batch option of trigger in Azure Pipelines YAML ?
trigger:
batch: 'true'
branches:
include:
- main
What is the difference between Individual CI and Batched CI in Azure Pipelines ?
How does it relate to the batch option of trigger in Azure Pipelines YAML ?
trigger:
batch: 'true'
branches:
include:
- main
How does it relate to the batch option of trigger in Azure Pipelines YAML ?
As the document Push trigger stated:
trigger:
batch: boolean # batch changes if true; start a new build for every push if false (default)
Explanation:
Build batching will take multiple commits and build them all at once in one batch instead of queuing each commit as a separate build which would extend the total time to build. If you are building code in Azure Pipelines and often find yourself waiting for queued builds. You may find it useful to enable build batching.
So, we could understand the state in that document now start a new build for every push if false (default). That means that if we set the value of this batch option to false, it will start a new build for every push (commit).
This is equivalent to our Batch changes while a build is in progress option in Classic mode: