Batching CI runs
If you have many team members uploadingchanges often, you may want to reduce the number of runs you start. If you set batch to true, when a pipeline is running, the system waits until the run is completed, then starts another run with all changes that have not yet been built.
Example:
# specific branch build with batching
trigger:
batch: true
branches:
include:
- master
To clarify this example, let us say that a push A to master caused the above pipeline to run. While that pipeline is running, additional pushes B and C occur into therepository. These updates do not start new independent runs immediately. But after the first run is completed, all pushes until that point of time are batched together and a new run is started.
Reference:
https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/github