[roll] Roll fuchsia [build][api] Add should_file_changes_trigger_build() function.

This new function will be used to implement a new command that
determines whether a build is necessary after files have been
changed due to a commit being applied to the source directory.

This is bound to replace the implementation of
//tools/integration/fint/should_build.go which is based
on `gn analyze` and thus cannot see any inputs added to
the Ninja graph through depfiles. In practice it means that
the current implementation cannot see Bazel build files
and input files at all, while this new function can.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1411716
Original-Revision: 3e4165385ccb3238eb0c9a2b5520291629edd545
GitOrigin-RevId: 193411e8bba76e253040f9c15f1bc701affdb09b
Change-Id: Ie910e89ca488c125ec000be22504aca32a20c3f1
1 file changed
tree: dd3bcb6e9d0de24eca794e3211346374013a488e
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
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.