Skip to content
sauce-labs-cli
Menu

Solutions

Solutions

One command per step, so a pipeline can script what you would otherwise click through in the dashboard.

See use cases

Upload each App file from CI

Upload the App file your pipeline just produced and pass its File id to the test step.

  • sauce storage upload prints only the File id, so ID=$(sauce storage upload ./app.ipa) captures it.
  • Credentials come from CI secrets exported as SAUCE_USERNAME and SAUCE_ACCESS_KEY.
  • A failed upload exits non-zero, so the job stops there.
Get started

Record results on Jobs

Mark jobs passed or failed and tag them with what your pipeline knows.

  • sauce jobs edit <id> --passed or --failed sets the Job result.
  • --build, --tag and --custom-data attach the pipeline’s build name, labels and any JSON object.
  • Only Virtual-device jobs can be edited.
Get started

Keep App Storage tidy

Find old App files and remove the ones you no longer need.

  • sauce storage files list --kind ios --query <term> finds candidates, one File id per line.
  • sauce storage info shows how long App Storage retains files.
  • sauce storage files delete removes one App file; it does not ask for confirmation.
Get started