tests: add non-blocking ci config for bazel rolling (#3272) With some core Bazel changes to flags coming that will affect us, and the difficulty it is to keep the bazel-at-head-and-downstream pipeline green, I figured it'd be a good idea to add a CI job that uses the weekly Bazel release so we can identify problems sooner and more obviously. The CI job only run on Ubuntu to save CI slots and is won't block merges if it has failures.
This repository is the home of the core Python rules -- py_library, py_binary, py_test, py_proto_library, and related symbols that provide the basis for Python support in Bazel. It also contains package installation rules for integrating with PyPI and other indices.
Documentation for rules_python is at https://rules-python.readthedocs.io and in the Bazel Build Encyclopedia.
Examples live in the examples directory.
The core rules are stable. Their implementation is subject to Bazel's backward compatibility policy. This repository aims to follow semantic versioning.
The Bazel community maintains this repository. Neither Google nor the Bazel team provides support for the code. However, this repository is part of the test suite used to vet new Bazel releases. See How to contribute page for information on our development workflow.
For detailed documentation, see https://rules-python.readthedocs.io
See Bzlmod support for more details.