ci: parallelize bazel build and test
The current setup can cause a de-optimization where unit tests can't start running until the slowest build target completes.
This commit is contained in:
parent
6e2a8a2ba4
commit
6d57cb04f6
|
@ -52,10 +52,14 @@ jobs:
|
||||||
<<: *post_checkout
|
<<: *post_checkout
|
||||||
- restore_cache:
|
- restore_cache:
|
||||||
key: *cache_key
|
key: *cache_key
|
||||||
|
|
||||||
- run: bazel info release
|
- run: bazel info release
|
||||||
- run: bazel run @yarn//:yarn
|
- run: bazel run @yarn//:yarn
|
||||||
- run: bazel build --config=ci packages/...
|
# Use bazel query so that we explicitly ask for all buildable targets to be built as well
|
||||||
- run: bazel test --config=ci packages/... @angular//...
|
# This avoids waiting for a build command to finish before running the first test
|
||||||
|
# See https://github.com/bazelbuild/bazel/issues/4257
|
||||||
|
- run: bazel query --output=label '//packages/... union @angular//...' | xargs bazel test --config=ci
|
||||||
|
|
||||||
- save_cache:
|
- save_cache:
|
||||||
key: *cache_key
|
key: *cache_key
|
||||||
paths:
|
paths:
|
||||||
|
|
|
@ -47,3 +47,6 @@ test --experimental_ui
|
||||||
|
|
||||||
# Don't be spammy in the continuous integration logs
|
# Don't be spammy in the continuous integration logs
|
||||||
build:ci --noshow_progress
|
build:ci --noshow_progress
|
||||||
|
|
||||||
|
# Don't run manual tests on CI
|
||||||
|
test:ci --test_tag_filters=-manual
|
||||||
|
|
Loading…
Reference in New Issue