tests: add non-blocking ci config for bazel rolling #3272
Merged
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
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.