Google Git
Sign in
bazel / rules_java / b48324c36309346df5322bf825c53bbec6ce8de6
commitb48324c36309346df5322bf825c53bbec6ce8de6[log] [tgz]
authorGoogler <hvd@google.com>Thu Jan 04 03:23:51 2024 -0800
committerCopybara-Service <copybara-worker@google.com>Thu Jan 04 03:24:17 2024 -0800
treeed1ea4c6f733acbbe73129a67152ed1da3f4813a
parent3abfbb86620f447c0e0e291eeec1ac29670b8c76 [diff]
Run some Bazel tests on `rules_java` presubmits

This should help catch (most) issues sooner and hopefully obviate the need to make Bazel PRs with unreleased `rules_java` archives.

This will also come in handy when migrating the rules out of `@builtins`.

For now, this is only for linux. I'll add testing on other platforms as a followup.

PiperOrigin-RevId: 595654881
Change-Id: I71d98e94921996155a3d9c68d89df2c1ab938409
3 files changed
tree: ed1ea4c6f733acbbe73129a67152ed1da3f4813a
  1. .bazel_checkout/
  2. .bazelci/
  3. .bcr/
  4. .github/
  5. distro/
  6. examples/
  7. java/
  8. toolchains/
  9. .bazelrc
  10. .bazelversion
  11. .gitignore
  12. AUTHORS
  13. BUILD
  14. CODEOWNERS
  15. CONTRIBUTING.md
  16. LICENSE
  17. MODULE.bazel
  18. README.md
  19. renovate.json
  20. WORKSPACE
  21. WORKSPACE.bzlmod
README.md

rules_java

  • Postsubmit Build status
  • Postsubmit + Current Bazel Incompatible Flags Build status

Java Rules for Bazel https://bazel.build.