[roll] Roll fuchsia [bazel] use correct compilation mode in refresh-bazel-compdb

The logic around how the build chooses its bazel compilation mode has
been updated which broke how we were refreshing the compilation
commands. This CL matches the logic we use in the build.

Users might need to run fx set before they can see the effects take
place.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1126622
Original-Revision: b3e0c9b08753eccf6f819f10e2f36c6f6d1b6a51
GitOrigin-RevId: ebf38fe8f7d3f7c6e41ccd04fe44a1b05118727c
Change-Id: I54906ff850fc3dde49e319e0019febd7a82b4672
1 file changed
tree: 05e7e948b2c07576f48f5a3f7491a0c0ace181d8
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.