Run Bazel build and stub builds in parallel for more performant builds #1177
Conversation
Instead of waiting for Bazel build to finish, we bring Bazel build to the background, and only check back for its status before copying outputs in the build of the requesting target.
|
There is a blocker with this approach: unable to disable the |
| @@ -186,7 +186,7 @@ $(BAZEL_INTEGRATION_DIR)/calculate_output_groups.py | |||
| name: name, | |||
| outputFileListPaths: outputFileListPaths, | |||
| shellScript: """ | |||
| "$BAZEL_INTEGRATION_DIR/bazel_build.sh" | |||
There was a problem hiding this comment.
And you could only do this in BwB mode, because in BwX, it needs generated sources. I think there might be other issues as well.
I like the idea though, and I hadn't considered backgrounding it. I was planning on something like this though where the various steps go as soon as they can, and I'll probably use this trick to accomplish it.
|
Will this cause the bazel build logs to no longer be available in Xcode though? |
|
Yeah, that's an issue as well. I think with Xcode 14 I'll be able to have the copy outputs scripts run in parallel to this job, without losing the output. When addressing #400 and #402, the goal is that only bazel-specific output is output here, and outputs for various compiles and linking are shown in the targets themselves. |
|
The bazel build logs are printed out at the end, so there will be a delay with warnings and errors. |
Instead of waiting for Bazel build to finish, we bring Bazel build to the background, and only check back for its status before copying outputs in the build of the requesting target.