-
Notifications
You must be signed in to change notification settings - Fork 54
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
bazel: adopt bzlmod #3116
bazel: adopt bzlmod #3116
Conversation
This comment was marked as off-topic.
This comment was marked as off-topic.
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.
nice
Will this require any changes to our renovate.json
?
As far as I can tell, renovate already natively supports bzlmod. Although I need to (and will) test if the |
52e8722
to
ecbfd6e
Compare
3rdparty/bazel/com_github_google_go_tpm_tools/com_github_google_go_tpm_tools.need
Outdated
Show resolved
Hide resolved
This change enables bzlmod without migrating any dependencies. Instead, WORKSPACE dependencies can be migrated one by one.
The mkosi_image rule uses a lot of memory. In order to allow higher levels of concurrency, such as `bazel build --jobs 128`, we need to more accurately model the amount of CPU and memory required.
e0412fb
to
5f79bc7
Compare
While it does have some quirks before Bazel 7.2, it is still vital for security.
Coverage report
|
Context
Bzlmod is the new dependency management system of Bazel. It works in a similar way as
go mod
.Proposed change(s)
Additional info
Checklist