Missing Linux yml

@TravisEz13 Could you please add more info about benefits of the change for my education?

@iSazonov See here:

https://docs.microsoft.com/en-us/azure/devops/pipelines/build/triggers?view=vsts&tabs=yaml#continuous-integration-ci

I could be missing some nuances also, but it appears that they're looking to batch together builds that originate from the same PR in order to allow Azure to queue a batch job if someone pushes a bunch of commits in quick succession; it will simply build them as one, shortening the overall build time. 🙂

@vexx32 Thanks. I still don't understand how it works really.

This does not batch PR builds. This batches merge (or as Azure DevOps calls them CI builds) while a merge build is in progress.

So if we merge PR A and a merge build starts.

Then we merge PR B and C while the build for PR A is still running, the next build will build B & C.

The feature @vexx32 mentioned is on by default.

Thanks @TravisEz13 !

Appreciate the clarification, looks like I gotta brush up on the yml spec once again! 😄