| commit | eaa38f5b6337f1f356c78b548ae3668f83e6e688 | [log] [tgz] |
|---|---|---|
| author | larsrc <larsrc@google.com> | Tue Jan 11 13:05:32 2022 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Jan 11 13:06:59 2022 -0800 |
| tree | 943bb29a680013f5ba9b7cb1f45ac7d9f2508211 | |
| parent | e4ef54e9985fc3632bfb14473ac5f9e5ced0a058 [diff] |
Reordering of DynamicSpawnStrategy:
- Move Branch, LocalBranch, RemoteBranch to their own files.
- Move exec{Local,Remote} to the branch classes - they still need to be static since they may be called before Branch objects get called.
- Move branchState() into Branch as an instance method.
- Move getSuffixedFileOutErr into Branch, it's only used there.
- Move remaining methods in DynamicSpawnStrategy around so they follow the logical flow: canExec() and its helper methods, followed by exec() and its helper methods, then branch termination handling.
This should not change functionality.
PiperOrigin-RevId: 421105510
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
