mirror of
https://github.com/SerenityOS/serenity
synced 2024-07-22 18:46:18 +00:00
10679b6df2
The CI system often develops a significant backlog when we have a lot
of PRs in the queue, and folks are pushing to master directly, or
other PRs are getting merged. The individual pushes to master or PR
merges to master each end up creating a dedicated master CI build.
These builds complete for machines with the normal PR validation builds.
To aid with this, Azure DevOps has a feature where they allow the CI
builds to "batch" multiple changes together, instead of running
multiple builds for each change.
Azure DevOps defines batching as:
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.
Documentation Reference:
https://docs.microsoft.com/en-us/azure/devops/pipelines/repos/github?view=azure-devops&tabs=yaml#batching-ci-runs
29 lines
480 B
YAML
29 lines
480 B
YAML
trigger:
|
|
batch: true
|
|
branches:
|
|
include:
|
|
- master
|
|
|
|
jobs:
|
|
- template: Meta/Azure/Lagom.yml
|
|
parameters:
|
|
os: 'Linux'
|
|
|
|
- template: Meta/Azure/Lagom.yml
|
|
parameters:
|
|
os: 'Linux'
|
|
fuzzer: 'Fuzz'
|
|
|
|
- template: Meta/Azure/Lagom.yml
|
|
parameters:
|
|
os: 'macOS'
|
|
allow_test_failures: true
|
|
|
|
- template: Meta/Azure/Serenity.yml
|
|
parameters:
|
|
arch: 'i686'
|
|
|
|
- template: Meta/Azure/Serenity.yml
|
|
parameters:
|
|
arch: 'x86_64'
|