[roll] Roll fuchsia [bazel] Generate remote_services.bazelrc file.

This is a reland of [1] which was reverted. Compare to patchset 1
on Gerrit to see what was changed.

[1] https://fuchsia-review.googlesource.com/c/fuchsia/+/1177873/7

------ original commit message -------------------------------

Instead of appending its content to bazel-workspace/.bazelrc,
write the content to a separate file, and make the `bazel`
launcher and `bazel_test.py` scripts use it directly.

This also moves the generate_remote_services_bazelrc target
to //build/bazel/bazel_sdk:remote_services_bazelrc, as it is
only used to run the Bazel SDK test suite without generating
anything with the internal Bazel workspace, as it happens
when generating and validating the Code IDK.

Original-Bug: 384956017
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1183712
Original-Revision: 455976f51a9067df3400df06033c40e2789268a6
GitOrigin-RevId: aea64fc9c3cdc6b6cc0b9724022516d21c6fa854
Change-Id: Ia9b9bfe494068d8e84ac5263afb0812082ff00c0
1 file changed
tree: 5b0ba0b1cb3ce19260d29c3dc5d684acec246b3d
  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.