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

Use same version of Bazel that is executing the test #100

Open
jfirebaugh opened this issue Dec 27, 2022 · 1 comment
Open

Use same version of Bazel that is executing the test #100

jfirebaugh opened this issue Dec 27, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@jfirebaugh
Copy link
Contributor

rules_bazel_integration_test might be used in a scenario where there's already scaffolding in place to run tests under different versions of Bazel. For example, with Bazel's own CI this might be configured as a test matrix where different rows of the matrix use a specific Bazel version. This could be used to execute an entire test suite, containing both unit and integration tests, with the same Bazel version.

Because this scaffolding would exist at a level higher than rules_bazel_integration_test, it would be desirable to configure rules_bazel_integration_test to simply use the same bazel binary that's executing the top-level bazel test command, rather than configuring an explicit binary via bazel_version or bazel_binary.

Is this something that could be supported?

@cgrindel
Copy link
Member

This is an interesting idea. What feature(s) from rules_bazel_integration_test would be useful in this situation? My mental model for rules_bazel_integration_test is that it provides a means for testing a Bazel ruleset from bootstrap through build/test from within the ruleset workspace. If there is an external system providing the matrix inputs, they could just run Bazel directly in the child workspace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants