-
Notifications
You must be signed in to change notification settings - Fork 5
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 Bazelisk and update to Bazel 7.4.0 #61
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,2 @@ | ||
common --config=rules | ||
common:v7.2 --config=rules_v7.2 | ||
common --config=rules | ||
import %workspace%/.bazelrc_shared |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,16 +20,5 @@ build --verbose_failures | |
|
||
test --test_output=all | ||
|
||
build:rules --disk_cache=.bazel_cache | ||
build:tests --disk_cache=../.bazel_cache | ||
|
||
common:rules_v7.2 --config=noop | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do you know what this deleted portion was doing? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The per version config existed so we could set flags for certain versions of Bazel and not others. Back before 1.0 things would change often enough that we'd often need a different set of flags for each version. Now that we're really only supporting 1 version of Bazel (because we only use these rules internally) we haven't had to do that for a while. The noop config was a way to have a version config that did nothing. The version configs were automatically generated by the old |
||
|
||
# route potentially unrouted configs to a terminating noop config | ||
# it's a noop because we use the default value | ||
common:rules --config=noop | ||
common:tests --config=noop | ||
common:v7.2 --config=rules_v7.2 | ||
|
||
# pick something trivial as a "noop" | ||
common:noop --logging=3 | ||
common:rules --disk_cache=.bazel_cache | ||
common:tests --disk_cache=../.bazel_cache |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
7.4.0 |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -14,9 +14,12 @@ jobs: | |
fail-fast: false | ||
matrix: | ||
os: [ubuntu-24.04] | ||
bazel_version: [7.2.0] | ||
bazel_version: [bazelbuild/7.4.0] | ||
steps: | ||
- uses: actions/checkout@v3 | ||
- uses: bazel-contrib/[email protected] | ||
with: | ||
bazelisk-version: 1.22.1 | ||
- run: ./scripts/ci.sh build | ||
- run: ./scripts/ci.sh lint | ||
- run: ./scripts/ci.sh test |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -7,8 +7,6 @@ | |
set -eox pipefail | ||
cd "$(dirname "$0")/.." | ||
|
||
. ./scripts/prepare-path.sh --force | ||
|
||
case "$1" in | ||
|
||
"build") | ||
|
This file was deleted.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
This file was deleted.
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.
Do you know why this existed to begin with?
Why have a
rules
section when we could just put those options under the commands themselves? E.g. instead ofbuild:rules --disk_cache=.bazel_cache
, we could dobuild --disk_cache=.bazel_cache
.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.
These configs existed because way back when Bazel was new the tests and rules had separate config.
Also because of us wanting to have a single place for the disk cache, which I realize I broke by removing this. I'll deal with that.