mobile-dev-inc/Maestro Cloud Upload Action

Upload your app to Maestro Cloud to run your Flows in CI

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
namedescriptionrequireddefault
api-urlAlternative mobile.dev API urlno
api-keymobile.dev API keyyes
nameName of the version of the uploaded appno
app-fileThe app file to upload to Maestro Cloudno
app-binary-idThe app binary already uploaded to Maestro Cloudno
mapping-fileThe Proguard mapping file to upload to Maestro Cloudno
workspacePath to a folder that contains Maestro flows (.maestro by default)no
branchBranch name to use for the upload metadata (overrides automatic detection).no
envSet of key=value entries to pass as an input to Maestro flowsno
asyncWhether to run Upload in async fashion and not block until completedno
android-api-levelAndroid API level (e.g. 33). Prefer 'device-os' (e.g. android-33).no
ios-versioniOS version (e.g. 18). Prefer 'device-os' (e.g. iOS-18-2).no
device-localeDevice locale to run your flow againstno
device-modelDevice model to run your flow againstno
device-osDevice OS to run your flow againstno
include-tagsList of tags that will remove flows that do not have the provided tagsno
exclude-tagsList of tags that will remove flows containing the provided tagsno
timeoutMinutes to timeout while waiting for resultsno
project-idMaestro Cloud project IDyes
maestro-cli-versionPin a specific Maestro CLI version (defaults to latest)no
namedescription
MAESTRO_CLOUD_APP_BINARY_IDID of the binary uploaded to Maestro Cloud
MAESTRO_CLOUD_CONSOLE_URLLink to the Maestro Cloud console for this upload
MAESTRO_CLOUD_UPLOAD_STATUSTerminal status of the upload (SUCCESS, ERROR, CANCELED, WARNING, STOPPED). Not set in async mode.
MAESTRO_CLOUD_FLOW_RESULTSJSON array of per-flow results (name, status, errors). Empty when --async or no junit report was produced.