| commit | 77b987524ad0988dd0d21cd5e9dcadb897bedd26 | [log] [tgz] |
|---|---|---|
| author | Laszlo Csomor <laszlocsomor@google.com> | Fri May 17 03:15:22 2019 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri May 17 03:17:27 2019 -0700 |
| tree | ebfeca3a7f0e30255cf9211f41233a6428e4ade6 | |
| parent | d824cb08f53e88f5f483498ff01f71c475ed6c1d [diff] |
file_test, rule_test: now as sh_test rules This commit rolls forward commit 76583ee114570e1866c1cc3842b40968e0119793, which was rolled back by commit 28f8af7c225cce1f06ea9f9bf4e3eb3b43835bd2. Differences: - test_rules.bzl:success_target and failure_target no longer dump 'msg' into a file and print that. Instead, they print it as a heredoc. - The same functions no longer need runfiles.bash. The breakage the original commit caused was that some Starlark rule used success_target but itself didn't depend on the Bash runfiles library, and success_target returns a DefaultInfo without the runfiles library in it. To keep existing success_target and failure_target calls intact, I opted to remove the dependency on runfiles.bash - marked all "_impl" rules as testonly=1 Original commit message follows. All test rules in @bazel_tools//tools/build_rule:test_rules.bzl are now macros around sh_test. This allows running them on Windows with the Windows-native test wrapper. Fixes https://github.com/bazelbuild/bazel/issues/8203 Unblocks https://github.com/bazelbuild/bazel/issues/6622 Closes #8352. PiperOrigin-RevId: 248691640
{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.