Deploy Fuchsia packages using 'pm publish' and a host-side HTTP server |
||||
Issue descriptionWe currently build a FAR for each package, which we SCP to the Fuchsia guest, then 'pm install' into blobfs. Deployment would be more efficient, especially for incremental changes (e.g. iterating on changes to a unit-test binary, without changing test data on which it depends), if we instead published the package's blobs to the guest for it to pull on-demand. The Fuchsia SDK's 'pm' tool provides 'pm publish' to create a blob directory from a set of files, and 'pm serve' to serve that to a device.
,
Oct 23
,
Oct 23
,
Dec 18
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b620d43ffd66907188bd9c83219e870e88424d96 commit b620d43ffd66907188bd9c83219e870e88424d96 Author: Kevin Marshall <kmarshall@chromium.org> Date: Tue Dec 18 12:42:53 2018 Fuchsia: Deploy packages using Amber HTTP blob pull mechanism. Replaces the existing scp & "pm install" based deployment workflow with one which provisions temporary TUF repositories, stages packages into the repo, and installs them onto the device using "amber_ctl get_up". Amber will pull in the blobs it needs via HTTP. Refactor port forwarding functions to common.py, as they are required by "pm serve". Bug: 895627 Change-Id: Ia2f9527d872bad19a2f245f0264b30279b303cad Reviewed-on: https://chromium-review.googlesource.com/c/1362248 Commit-Queue: Kevin Marshall <kmarshall@chromium.org> Reviewed-by: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#617457} [modify] https://crrev.com/b620d43ffd66907188bd9c83219e870e88424d96/build/config/fuchsia/rules.gni [modify] https://crrev.com/b620d43ffd66907188bd9c83219e870e88424d96/build/fuchsia/common.py [modify] https://crrev.com/b620d43ffd66907188bd9c83219e870e88424d96/build/fuchsia/net_test_server.py [modify] https://crrev.com/b620d43ffd66907188bd9c83219e870e88424d96/build/fuchsia/qemu_target.py [modify] https://crrev.com/b620d43ffd66907188bd9c83219e870e88424d96/build/fuchsia/run_package.py
,
Dec 18
,
Jan 12
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0daf72ec0ca1b77b1617843f33dd8300b8b7748d commit 0daf72ec0ca1b77b1617843f33dd8300b8b7748d Author: Kevin Marshall <kmarshall@chromium.org> Date: Sat Jan 12 02:28:13 2019 [fuchsia] Make `pm serve` run silently. "pm serve" runs reliably and no longer needs to run verbosely. The remaining issues with amber-based deployments tend to be on the device, not on the HTTP server. This change prevents a lot of httpd log spam from being sent to the console. Bug: 895627 Change-Id: If5e63785c8d70568bd4b1b99a18f4c59acc2a48e Reviewed-on: https://chromium-review.googlesource.com/c/1407255 Commit-Queue: Kevin Marshall <kmarshall@chromium.org> Commit-Queue: Wez <wez@chromium.org> Reviewed-by: Wez <wez@chromium.org> Cr-Commit-Position: refs/heads/master@{#622272} [modify] https://crrev.com/0daf72ec0ca1b77b1617843f33dd8300b8b7748d/build/fuchsia/run_package.py |
||||
►
Sign in to add a comment |
||||
Comment 1 by w...@chromium.org
, Oct 15