[roll] Roll fuchsia [devshell] Add cleanrepo and cleanrepo-build

This adds simple functionality to remove the repository and keys in
FUCHSIA_BUILD_DIR/amber-files while keeping the options file for
publish_tool. Over time, when developers regularly run `fx build`, the
repository can become quite large, since old blobs are not deleted
automatically. If these are no longer neened, purging the repo and
rebuilding it in the subsequent `fx build` is often useful to save
space.
Also, in the same style as `cleandead` and `clean`, this also adds
`cleanrepo-build` which runs a full build after removing the repo. If
the build is up-to-date and was successfully completed previously, this
ends up merely publishing the repo and takes only a few seconds.

Original-Bug: b/409838702
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1479196
Original-Revision: e712df42ea233b27328427edfeccfe6f7c41f646
GitOrigin-RevId: 77034f8431a3b471838d7fd060e758bc7ecf25f5
Change-Id: Ied0bf56325a0908909d7b46e4ac502a640e25374
1 file changed
tree: 9478d062a00af22fdc1f7c1a40fac66c0acf24f6
  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.