1
0
Fork 0
mirror of https://github.com/imjasonh/gcloud-help synced 2026-07-08 02:25:19 +00:00

gcloud: Thu Feb 23 10:13:49 UTC 2023

This commit is contained in:
Automated 2023-02-23 10:13:49 +00:00
parent 78fb6d9419
commit 7664984b79
46 changed files with 947 additions and 130 deletions

View file

@ -64,3 +64,11 @@ GCLOUD WIDE FLAGS
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test android list-device-capacities
$ gcloud beta firebase test android list-device-capacities

View file

@ -7,6 +7,7 @@ SYNOPSIS
[--device=DIMENSION=VALUE,[...]] [--test=TEST] [--timeout=TIMEOUT]
[--type=TYPE] [--additional-apks=APK,[APK,...]]
[--app-package=APP_PACKAGE] [--async] [--auto-google-login]
[--client-details=[KEY=VALUE,...]]
[--directories-to-pull=[DIR_TO_PULL,...]]
[--environment-variables=[KEY=VALUE,...]]
[--network-profile=PROFILE_ID] [--num-flaky-test-attempts=int]
@ -227,6 +228,25 @@ FLAGS
account before beginning the test. Enabled by default, use
--no-auto-google-login to disable.
--client-details=[KEY=VALUE,...]
Comma-separated, KEY=VALUE map of additional details to attach to the
test matrix. Arbitrary KEY=VALUE pairs may be attached to a test matrix
to provide additional context about the tests being run. When consuming
the test results, such as in Cloud Functions or a CI system, these
details can add additional context such as a link to the corresponding
pull request.
Example:
--client-details=buildNumber=1234,pullRequest=https://example.com/link/to/pull-request
To help you identify and locate your test matrix in the Firebase
console, use the matrixLabel key.
Example:
--client-details=matrixLabel="Example matrix label"
--directories-to-pull=[DIR_TO_PULL,...]
A list of paths that will be copied from the device's storage to the
designated results bucket after the test is complete. These must be

View file

@ -64,3 +64,11 @@ GCLOUD WIDE FLAGS
--trace-token, --user-output-enabled, --verbosity.
Run $ gcloud help for details.
NOTES
These variants are also available:
$ gcloud alpha firebase test ios list-device-capacities
$ gcloud beta firebase test ios list-device-capacities

View file

@ -6,7 +6,8 @@ SYNOPSIS
gcloud firebase test ios run [ARGSPEC] [--device=DIMENSION=VALUE,[...]]
[--test=XCTEST_ZIP] [--timeout=TIMEOUT] [--type=TYPE]
[--xcode-version=XCODE_VERSION] [--xctestrun-file=XCTESTRUN_FILE]
[--app=APP] [--async] [--num-flaky-test-attempts=int] [--record-video]
[--app=APP] [--async] [--client-details=[KEY=VALUE,...]]
[--num-flaky-test-attempts=int] [--record-video]
[--results-bucket=RESULTS_BUCKET] [--results-dir=RESULTS_DIR]
[--results-history-name=RESULTS_HISTORY_NAME]
[--test-special-entitlements] [--filter=EXPRESSION] [--limit=LIMIT]
@ -30,6 +31,12 @@ DESCRIPTION
for more information about argument files.
EXAMPLES
To help you identify and locate your test matrix in the Firebase console,
run:
$ gcloud firebase test ios run --test=XCTEST_ZIP \
--client-details=matrixLabel="Example matrix label"
To invoke an XCTest lasting up to five minutes against the default device
environment, run:
@ -136,6 +143,25 @@ FLAGS
--async
Invoke a test asynchronously without waiting for test results.
--client-details=[KEY=VALUE,...]
Comma-separated, KEY=VALUE map of additional details to attach to the
test matrix. Arbitrary KEY=VALUE pairs may be attached to a test matrix
to provide additional context about the tests being run. When consuming
the test results, such as in Cloud Functions or a CI system, these
details can add additional context such as a link to the corresponding
pull request.
Example:
--client-details=buildNumber=1234,pullRequest=https://example.com/link/to/pull-request
To help you identify and locate your test matrix in the Firebase
console, use the matrixLabel key.
Example:
--client-details=matrixLabel="Example matrix label"
--num-flaky-test-attempts=int
Specifies the number of times a test execution should be reattempted if
one or more of its test cases fail for any reason. An execution that