| commit | 9d3689b43c0cc6b9328c26c94544e888c5481ebc | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Wed Oct 14 08:17:44 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Oct 14 08:18:54 2020 -0700 |
| tree | 07f70bc43c0fd28b04f1f93caede74a12b556feb | |
| parent | 60a69b43a6b72b49094f69e4fb0be56e54293580 [diff] |
Remove Artifact#getOutputDirRelativePathString. * StarlarkActionFactory - It's part of a progress message. getExecPathString serves the purpose well enough. * AndroidBinaryTest - This test doesn't deal with external repository artifacts, so it can be replaced with getRepositoryRelativePathString. * BazelJavaSemantics - Given the path strings are prefixed with a workspace name, getRepositoryRelativePathString is the right method to use. PiperOrigin-RevId: 337093765
{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:
See CONTRIBUTING.md
