Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing bzlmod earlier #119

Merged
merged 2 commits into from
Sep 25, 2023
Merged

Testing bzlmod earlier #119

merged 2 commits into from
Sep 25, 2023

Conversation

linzhp
Copy link
Contributor

@linzhp linzhp commented Sep 24, 2023

bzlmod requires a different flag to override external dependencies. We need to parameterize that flag depending on whether an example has bzlmod enabled. With this change, our CI covers the the case of a test module depending on hermetic_cc_toolchain as a bazel_dep, pointing to a release archive created from HEAD and running all tests in the test module. Hopefully we can catch issues in our CI, rather than on BCR's CI after a release is cut.

With this change, we no longer run the tests again in BCR's CI and no longer need to include the example in the release archive. We only need to verify that the latest release can be loaded by the anonymous test module.

@linzhp linzhp requested review from motiejus and sywhang September 25, 2023 00:12
@linzhp linzhp merged commit a8d21f4 into uber:main Sep 25, 2023
@linzhp linzhp deleted the bcr_ci branch September 25, 2023 02:55
Antonito pushed a commit to tentenapp/hermetic_cc_toolchain that referenced this pull request Sep 25, 2023
bzlmod requires a different flag to override external dependencies. We
need to parameterize that flag depending on whether an example has
bzlmod enabled. With this change, our CI covers the the case of a test
module depending on hermetic_cc_toolchain as a `bazel_dep`, pointing to
a release archive created from HEAD and running all tests in the test
module. Hopefully we can catch issues in our CI, rather than on BCR's CI
after a release is cut.

With this change, we no longer run the tests again in BCR's CI and no
longer need to include the example in the release archive. We only need
to verify that the latest release can be loaded by the [anonymous test
module](https://github.com/bazelbuild/bazel-central-registry/blob/main/docs/README.md#anonymous-module-test).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants