[roll] Roll fuchsia Reland "[bazel] Do not propagate defines to the exec config" This is a reland of commit fda1f2cd566692ace0ae7b90bdffd8503e83895b Explicitly propagate `EXECUTOR`, which is used in remote builds, so the same strategy is used in the exec config. This is also necessary to avoid diffs on the `core.x64-asan-bazel_consistency` bot. Original change's description: > [bazel] Do not propagate defines to the exec config > > Add an experimental flag prevent defines from propagating to > the exec config where host tools used in the build are built. > > There are no known issues, but it seems better to avoid any > unintentional propagation and potential performance impacts. > > Original-Bug: 478893794 > Change-Id: If732cc0c129352c2a41a7d4ad2227e0fed1a37fa > Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1485317 > Reviewed-by: David Turner <digit@google.com> > Commit-Queue: David Dorwin <ddorwin@google.com> Original-Bug: 481735598 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1492884 Original-Revision: 9a722eeb5b9a43c60270c1c90308559c8e405759 GitOrigin-RevId: 263dd0933bbdb7ba2dcd1f114ce37e5f00e562c8 Change-Id: I044b9fe0bdeba1492898edd3371bd0398c496332
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.