[roll] Roll fuchsia [bazel] Re-run @prebuilt_llvm when LLVM changes generate_prebuilt_llvm_repository populates @prebuilt_llvm by running symlink-directory.py over the LLVM prebuilt, and Bazel can't track inputs used only inside rctx.execute(). So nothing caused the repository to be re-run when the LLVM prebuilt rolled, other than the regenerator's wholesale wipe of output_base/external. Give it a content hash file and watch it, the same way @prebuilt_clang and the Rust toolchain repositories already do. LLVM is a separate CIPD package from clang, so it gets its own hash rather than reusing prebuilt_clang.hash. TAG=agy CONV=46a53854-81aa-49db-874c-3a81367d1c46 query re-ran the @prebuilt_llvm repository rule, while an unchanged re-query did not. Original-Original-Bug: 567975215 Test: Changed prebuilt_llvm.hash and confirmed that the next bazel Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1860755 Original-Original-Revision: d5b50acca85d49a641ad07ab93498b99f58c3907 GitOrigin-RevId: 06b78a3aec9a92313a52f07baa25eefc8620bf61 Change-Id: Ibe6142f1ec0770e96c687e16d9a148c007f83065 Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1861219 Cr-Commit-Position: refs/heads/main@{#203977}
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.