commit | 7d31cd7ad1a46c3f9764c720e1850fdd98948e42 | [log] [tgz] |
---|---|---|
author | aiuto <aiuto@google.com> | Thu Jul 25 20:28:40 2019 -0700 |
committer | Copybara-Service <copybara-worker@google.com> | Thu Jul 25 20:29:43 2019 -0700 |
tree | ec39a3a9ceaf487cf9ee6562c229f182df0874dc | |
parent | 21aadcb444fb90494c7954b0e5b6021a56331987 [diff] |
Switch Android rules runtime deps builder to use rules_pkg for pkg_tar. See https://github.com/bazelbuild/bazel/issues/8857 Thoughts: - The change to discard_graph_edges_test.sh is ridiculous. The test is flaky in CI and super brittle. - The fact that some integration tests rely on a WORKSPACE that matches that used to build bazel is odd. I should be able to use the built version of Bazel with my own workspace, with rules_cc and rules_pkg at a different revision level. We should have an integration test framework which establishes an entirely different WORKSPACE and runs a variety of tests within that, rather than trying to build a special purpose one for each test. RELNOTES: None PiperOrigin-RevId: 260074256
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds 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
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.