Bitrise Build Cache now tells you what broke in a failed Bazel build.
Every Bazel invocation page lists its targets with a pass or fail status, and every failed target opens up to show the actions that failed, including the compiler output itself.
Until now a red Bazel invocation told you only that it failed. Finding the cause meant scrolling the raw build log, hunting for the first ERROR: line, and working backwards to the target that produced it.
Now the page answers that directly:
- Status on every target, so a build with hundreds of targets shows you the handful that actually failed.
- Failed actions grouped under their target: one broken library can fail several separate compile actions, and they are listed together rather than scattered through a log.
- The action’s own output, inline. The exact compiler error, exit code and action type for each failure, so you can read the diagnosis without leaving the page.
This is especially handy with Bazel Remote Build Execution, where the failing action ran on a remote worker that’s already gone by the time you look. Its output is captured and shown on the invocation page like any other failure, so a remote build is no harder to debug than a local one.
Nothing new to turn on. Failure details come from the build event stream your builds already send us, so if you set Bazel up by following our guide - on Bitrise CI or anywhere else - they appear automatically on your next failed invocation. Open Build Cache → a failed Bazel invocation, and the failing targets are the first thing you’ll see.
Happy debugging! 