051b0111ea
The main purpose of the PR is to add bandwidth checker capabilities to push copies. However, since there is also a desire to move the checker into the gRPC copier, much more changes were required. Moved the `BandwidthChecker` into the gRPC copier instead of having a `BandwidthCheckedCopier`. This is desirable because now the checker won't be checking connection time and it'll measure just while streaming content. As with normal copies, different attempts can have different bandwidth requirements. This is achieved by `DistributedContentCopier`. I felt it was important for this logic to live entirely in one place, since this is all an effort to consolidate the behavior pushed and pulled copies. As an additional quality of life improvement, we will now log the time spent connecting to the server when the copy is successfully attempted, so that we can differentiate between time spent copying and time spent connecting. |
||
|---|---|---|
| .config | ||
| .vscode | ||
| Documentation | ||
| Examples | ||
| Private | ||
| Public | ||
| Shared | ||
| cg | ||
| third_party | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| BuildCache.cmd | ||
| BuildCacheDefault.json | ||
| BuildCacheDefaultNetCore.json | ||
| BuildCacheOverride.json | ||
| CODEOWNERS | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| CreatePr.cmd | ||
| LICENSE | ||
| README.md | ||
| RunCheckInTests-Test.cmd | ||
| RunCheckInTests.cmd | ||
| RunCheckInTestsWithPAT.ps1 | ||
| SECURITY.md | ||
| SlimBuildForMacTests.cmd | ||
| buddy.cmd | ||
| bxl.cmd | ||
| bxl.sh | ||
| bxlanalyzer.cmd | ||
| clean.bat | ||
| config.dsc | ||
| config.microsoftInternal.dsc | ||
| config.nuget.aspNetCore.dsc | ||
| config.nuget.dotnetcore.dsc | ||
| config.nuget.grpc.dsc | ||
| config.nuget.vssdk.dsc | ||
| domino.cmd | ||
| drop.cmd | ||
| dropout.cmd | ||
| macos.mounts.dsc | ||
README.md
Microsoft Build Accelerator
Introduction
Build Accelerator, BuildXL for short, is a build engine originally developed for large internal teams at Microsoft, and owned by the Tools for Software Engineers team, part of the Microsoft One Engineering System internal engineering group. Internally at Microsoft, BuildXL runs 30,000+ builds per day on monorepo codebases up to a half-terabyte in size with a half-million process executions per build, using distribution to thousands of data center machines and petabytes of source code, package, and build output caching. Thousands of developers use BuildXL on their desktops for faster builds even on mega-sized codebases.
BuildXL accelerates multiple build languages, including:
- MSBuild (using new features under development in MSBuild 16 which will ship in future versions of Visual Studio 2019 and the .NET Core SDK)
- CMake (under development)
- Its own internal scripting language, DScript, an experimental TypeScript based format used as an intermediate language by a small number of teams inside Microsoft
BuildXL has a command-line interface. There are currently no plans to integrate it into Visual Studio. The project is open source in the spirit of transparency of our engineering system. You may find our technology useful if you face similar issues of scale. Note that BuildXL is not intended as a replacement for MSBuild or to indicate any future direction of build languages from Microsoft.
Documentation
The BuildXL documentation main page is here.
Examples and Demos
See the Examples/ folder for basic project examples. See the Demos page for information about various technical demos like using the process sandboxing code.
Building the Code
Build Status - Azure DevOps Pipelines
Command Line Build and Test
See the Developer Guide for instructions on compiling BuildXL.
Contributing
See CONTRIBUTING.