Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reduce incidence of build storms #3079

Merged
merged 4 commits into from
Nov 8, 2021
Merged

Conversation

danieljurek
Copy link
Member

  • Narrow build targeting
  • Use batching so changes to main don't trigger builds for every checkin if there are other builds running docs
  • Expand core CI to test everything (this may not be sustainable as projects grow) ... A sparse testing matrix in these scenarios may be preferable.

…don't trigger builds for every checkin if there are other builds running, expand core to test everything in CI
@danieljurek danieljurek requested a review from a team as a code owner November 8, 2021 14:56
@ahsonkhan ahsonkhan added the EngSys This issue is impacting the engineering system. label Nov 8, 2021
@@ -1,5 +1,6 @@
# NOTE: Please refer to https://aka.ms/azsdk/engsys/ci-yaml before editing this file.
trigger:
batch: true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Anything in particular that motivated us to start using batch now? I think this change generally makes sense to be more efficient, but I am assuming, it could make finding the exact commit which caused a build failure to be a bit difficult. Do I understand it correctly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EngSys This issue is impacting the engineering system.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants