[roll] Roll fuchsia [fx set] Rebuild fx-set if JIRI_HEAD changes By recording the current JIRI_HEAD to a file after building the `fx-set` executable, and rebuilding on later invocations only if JIRI_HEAD differs from the revision stored in the cached file. This will ensure that if a developer runs `fx set` several times in a row between `jiri update` invocations, it won't take the 0.3-0.5 seconds to rebuild the fx-set executable every time. The previously attempted approach (deleting the cached executable in a Jiri hook and rebuilding only if the executable is missing) was somewhat fragile because it relied on a contract between integration.git and fuchsia.git, as the hook declared in integration.git would break if using a version of fuchsia.git that didn't contain the expected script. In contrast, this new approach avoids those issues by being completely contained within fuchsia.git. Original-Bug: 68465 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/506280 Original-Revision: 160ae0e9a7ece6e9c7c69f22d0bac4d348722508 GitOrigin-RevId: d0b6ab4b4bab7e91e69999b72ba9c2e8f2d943c5 Change-Id: Ie2c0682d2cdb040b8d545a760d31b6d26454d0f2
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 via the IRC channel #fuchsia on Freenode.
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.