7 Commits

Author	SHA1	Message	Date
Brian Gianforcaro	10679b6df2	CI: Batch master builds in Azure DevOps to help with CI latency ... 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	2021-09-12 18:41:57 +00:00
Timothy Flynn	e3d4778a63	CI: Build Lagom with fuzzing on Azure	2021-08-17 21:06:15 +01:00
Timothy Flynn	3ce6f26924	CI: Build and test SerenityOS with the Clang toolchain on Azure	2021-08-17 13:31:43 +01:00
Timothy Flynn	27804a6e67	CI: Build and test Lagom (non-fuzzer) on Azure	2021-08-16 18:04:33 +01:00
Linus Groh	87b2a6004f	CI: Add a hello world step to azure-pipelines.yml so it stops failing	2021-08-14 22:43:34 +01:00
Linus Groh	6f9b87948b	CI: Add required stages parameter to azure-pipelines.yml	2021-08-14 22:35:24 +01:00
Linus Groh	a548366425	CI: Set up Azure Pipelines ... [skip ci]	2021-08-14 20:29:20 +01:00