-
Notifications
You must be signed in to change notification settings - Fork 18
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
wip: adopt bzlmod #75
Closed
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
manuelnaranjo
force-pushed
the
mnaranjo/bzlmod
branch
8 times, most recently
from
July 15, 2024 15:05
cfc6595
to
3f51d00
Compare
Ok now this works as expected, I can consume it from our MODULE.bazel with:
Will cleanup the branch so we can merge the initial bzlmod support |
Using a matrix instead of copying the test structure so many times
Prebuilts are now handled differently and require a proper release process, in order to allow forks to also release we need to consume GITHUB_REPOSITORY while rendering the repo files.
There were quite a few missing things from my merged code this should fix it
When building bazeldnf we now use bzlmod as well
updating build files to match the latest gazelle settings
adding bazel6 bzlmod test
now we have a step to validate buildifier
We no longer need this bzl file with bzlmod and rules_go go.mod support
following the suggestions from bazeldnf linter
ctx.actions.args is a more efficient way of dealing with arguments that get passed into actions
heaviliy inspired in https://github.com/aspect-build/bazel-lib which also provides a few prebuilt golang binaries
now while archiving we stamp the content
Make sure platforms are available accross the entire repository and not only in bazeldnf/private
Making sure github keeps bazel cache around
fixing small issue with the legacy external API
We have no config for release, no need to pass this flag
We need to execute the release target instead of build
We don't need to support the multiple versions approach suggested by the templates repo, we're closer to aspect-bazel-lib than to a wrapper for already available tools
when building the tool it self we can use bazel 7
Stop waisting valuable CI time in protoc building
Closing the loop
manuelnaranjo
force-pushed
the
mnaranjo/bzlmod
branch
from
July 16, 2024 11:07
874c051
to
ef3f17f
Compare
Finally there with #77 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TBD
I need to revist the list of commits and squash a few most likely