| commit | c5eb66cafb6b9f245d07cc3634fea0326f46759d | [log] [tgz] |
|---|---|---|
| author | Venkatesh Srinivas <venkateshs@google.com> | Thu Dec 13 19:52:49 2018 +0000 |
| committer | CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> | Tue Dec 18 00:33:00 2018 +0000 |
| tree | e527ccf9ede3f671d7d829c1159f2d4719cf65ef | |
| parent | e7e66e595a4d3acf63eecb3326b42f62f9dfea44 [diff] |
[gce] Use pigz if available to compress fx disk image fx gce create-fuchsia-image constructs a fuchsia disk image suitable for GCE; the image is a raw disk image inside a gzipped tarball. One of the slower steps of constructing the disk image is gzipping the tarball; use pigz (parallel gzip) if available to save time. On a Xeon 'Skylake' 24 vCPU GCE instance, reduces the time for compression in create-fuchsia-image from 2 min to 9 seconds. Change-Id: Ic880890737f6af585f6e91406655097cd79dbab6
This repository is for scripts useful when hacking on Fuchsia. This repository should contain scripts that perform tasks spanning multiple repositories. Scripts that only operate within a single repository should live in the relevant repository.
The push-package.py script pushes the files listed in the given manifests files. No checking is performed for incremental changes.
The sample command lines below can be used to build Modular and then push those files to the default device. This assumes you have already booted your device with a version of Fuchsia that contains the most recent version of all other packages. This command line uses the “system_manifest” file from each of the modular directories, such as modular, modular_dev, and modular_tests.
cd $FUCHSIA_DIR fx build peridot:modular_all scripts/push-package.py out/debug-x64/package/modular*/system_manifest
fx publish will take a package from the build and create a Fuchsia package manager package from a build package. It will then add the package to a local update respository which, by default, is put at ${FUCHSIA_BUILD_DIR}/amber-files. It will also add the package content files to the update repository and name these file after their Merkle Root. If a package name is supplied to fx publish, only that package will be processed. If no name is supplied, all the packages made by the build will be included.