tree 19bf4beee21efac72301711cd518609ac3d1ba72
parent 2cbdc1b57bb7591577fbf406d499ce403af067a6
author Richard Levasseur <rlevasseur@google.com> 1703143668 -0800
committer GitHub <noreply@github.com> 1703143668 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJlg+kDCRBK7hj4Ov3rIwAAarAIAI9eHAdu+sNNw50KSiMYRnMP
 6Uxk50KxBEIwfAmbs9zPDItzMU0wX/T4VRZ9VSlWFstfV976OnVcgfVZfj+sRhUg
 /JUKooLQqpDk2nqLpx7w1vqLJwrYv2YRhy8iqRlivosBgXicQIXbKnWnSsH2pqCh
 pz9FNHizPKKo98c4oQ9aAT4xJ+ekNva7xYsE5RHYn2IwD+CTwrST5tZY1D3KlvSJ
 uAdD8UB7aQn++zFtbAPmuCJ+q0Uxsj389iglfTZ3HCrw42EV9/f/BpMdyHSDFerD
 zC3shdccq83PJD/HJyxM2FyhL/06HhUsbG/FAwTBL3uWdFeDXHfrJg9YEl3/qkc=
 =anuW
 -----END PGP SIGNATURE-----
 

chore: enable bzlmod by default (for Bazel 6) (#1632)

This enables bzlmod by default so that, by default, builds are using it
for both Bazel 6
and Bazel 7.

This exposed some gaps in our test coverage, so some new jobs are
created to cover
minimum bzlmod and workspace versions. Basically, our CI config used
mostly
workspace builds, while Bazel's downstream testing used bzlmod builds.
Changing
our config to default to bzlmod means we lost most workspace build
coverage.

Unfortunately, adding these new jobs goes over the CI job limit, so I
consolidated
tests a bit:
* The py_proto_library example for bzlmod is moved under the bzlmod
example. This saves
  about 6 jobs
* Change some tests with both (Bazel 7, workspace) and (Bazel 6,
workspace) to have
just one of the two. This saves about 4 jobs. Many jobs still test both,
so coverage
  should still be sufficient.

Also some various cleanups:
* Deletes the last bazel-in-bazel integration test using our old,
private, fork of
bazel_integration_test. It hasn't been running in a long time and is
broken.
* Renames the CI jobs to have shorter names.