| commit | 94524d275707e0a1bb3773435b72e905425fe6b4 | [log] [tgz] |
|---|---|---|
| author | Gary Boone <gboone@fuchsia.infra.roller.google.com> | Wed Jul 20 21:38:21 2022 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jul 20 14:39:52 2022 -0700 |
| tree | 1c67d9ccb54273e4424ce908e67f7dd8d6b9fdfb | |
| parent | c4c49380b4e91ea062bc4e606ed8e845631e244e [diff] |
[roll] Roll fuchsia [dash-launcher] Add inline commands to explore
As a partial step toward enabling scripting in component explore,
this CL adds a `-c <command> parameter to `ffx component explore`,
enabling commands to be executed directly by the Dash shell on the
target.
When a `-c` command is given, ffx returns immediately after running
the command and does not enter interactive mode
Example:
$ ffx component explore /bootstrap/archivist -c "ls exposed"
diagnostics
fuchsia.diagnostics.ArchiveAccessor
fuchsia.diagnostics.FeedbackArchiveAccessor
fuchsia.diagnostics.LegacyMetricsArchiveAccessor
fuchsia.diagnostics.LoWPANArchiveAccessor
fuchsia.diagnostics.LogSettings
fuchsia.logger.Log
fuchsia.logger.LogSink
Limitations:
• The exit status after executing a command is the exit status of the
explore command, not the exit status of the executed command.
The executed command's exit status can be obtained by echoing it as
part of the command string. Eg:
$ ffx component explore /bootstrap/archivist 'rm no_such_file; echo $?'
rm: lstat no_such_file: No such file or directory
1
This issue is tracked in fxb/104633
Original-Bug: 104305
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/700627
Original-Revision: fac225141ab884e77bc538cc578e159db1803d6f
GitOrigin-RevId: 1afda6f767b5b9018bbfa76dbe295c9791f9ef21
Change-Id: I3fc0ddafaca2b0c9ac691c0548a01e8930d25318
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.