Skip to content

Add publish-to-bcr configuration #64

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

Merged
merged 3 commits into from
Jan 7, 2023

Conversation

jsharpe
Copy link
Member

@jsharpe jsharpe commented Jan 6, 2023

Adds configuration for the publish-to-bcr app which auto publishes a PR to the bazel-central-registry whenever a release is made.

@@ -0,0 +1,12 @@
# We recommend included a bcr test workspace that exercises your ruleset with bzlmod.
# For an example, see https://github.com/aspect-build/bazel-lib/tree/main/e2e/bzlmod.
#bcr_test_module:
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can't run tests in the registry until we have a hermetic toolchain as there will be no cuda install in bazelbuild CI

Comment on lines +4 to +8
{
"email": "james.sharpe@zenotech.com",
"github": "jsharpe",
"name": "James Sharpe"
}
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@cloudhan @ryanleary note that this is the maintainer of the BCR entry not necessarily the repo; feel free to add yourself to this list if you want but I'm happy to be listed here.

@jsharpe
Copy link
Member Author

jsharpe commented Jan 6, 2023

Once this is merged we can try cutting a release and it should post a PR to the central registry to add rules_cuda as a module.

@jsharpe jsharpe merged commit 17ca7f8 into bazel-contrib:main Jan 7, 2023
@jsharpe jsharpe deleted the publish-to-bcr branch January 7, 2023 10:09
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