-
Notifications
You must be signed in to change notification settings - Fork 0
Publish to bcr config #1
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
Conversation
.bcr/presubmit.yml
Outdated
bazel: ${{ bazel }} | ||
test_targets: | ||
- "//examples/internal/..." | ||
- "//:all" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This target does not exist, and I don't know if it makes sense to add this when we only really want to build the examples.
- "//:all" |
@@ -0,0 +1,13 @@ | |||
bcr_test_module: | |||
module_path: "MODULE.bazel" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I recall our original conversation correctly, we were discussing the possibility of creating a small test project within the grpc-gateway
repo to run the pre-submit with. This project would import the grpc-gateway
Bazel module and build the examples with it. That way, we would be testing the entire bzlmod
pipeline.
If that is the case, we would have to create a MODULE.bazel
file in the examples
directory and configure it to import the grpc-gateway
Bazel module, and update this configuration so to import that module instead.
module_path: "MODULE.bazel" | |
module_path: "examples/MODULE.bazel" |
At this point, you are probably better informed than I am as to how to proceed with the pre-submit check, but I didn't want to approve without asking if the current configuration is intentional.
Thanks for looking into this, please let me know what, if anything, you need me to help with. |
2a698f3
to
5826a0c
Compare
References to other Issues or PRs
This is a follow-up work for the issue: Consider publishing grpc-gateway to Bazel Central Registry #5183
Have you read the Contributing Guidelines?
Yes
Brief description of what is fixed or changed
This PR aims to add the templates for the Publish to the Bazel Central Registry - BCR process.
The process is described in bazel-contrib/publish-to-bcr
Other comments