Skip to content

docs(cli): document build list, build download and baseline download - #266

Merged
gregberge merged 1 commit into
mainfrom
docs/cli-build-baseline-download
Oct 21, 2026
Merged

gregberge merged 1 commit into
mainfrom
docs/cli-build-baseline-download

Conversation

@gregberge

@gregberge gregberge commented Oct 21, 2026 •

Copy link
Copy Markdown
Member

Documents the three commands added to @argos-ci/cli in argos-ci/argos-javascript#405 (ARG-522: export a project's screenshots and baselines).

Merge this once the CLI release that ships them is out. They land in the next minor after 6.10.0, which should be 6.11.0 (Lerna + conventional commits). That version is an assumption: it isn't released yet. The docs don't add version notes for CLI features, so this PR doesn't either.

What's documented

CLI reference (docs/sdks-reference/argos-command-line-interface-cli.md), written as prose plus examples like the other commands on the page, since the page leaves full flag lists to --help:

  • Commands table: build list, build download <buildReference>, baseline download.
  • Token rules: build list and build download work with a project token. baseline download only accepts a project token and reads that token's own project, so it has no --project and rejects personal access tokens, including the argos login one.
  • Inspecting builds and tests: build list, with --branch, --commit (full 40-character SHA only), --search (build name, branch substring, commit prefix), and --project / ARGOS_PROJECT for personal access tokens.
  • New section, Downloading screenshots and baselines:
    • build download defaults to ./argos-build-<number>, fails while the build is processing, and skips removed snapshots.
    • baseline download picks the newest build on the default baseline branch that is eligible as a baseline, linking to the baseline page's eligibility rules (it uses the same criteria as the "Eligible as baseline" chip). It covers --branch, --build-name (default default, one name at a time), --mode, the omitted failure screenshots, the 1,000-build search window and the "No baseline found" error.
    • Shared behavior: the output directory must be empty or not exist yet, files are laid out by snapshot name, extensions are kept or derived (including JPEGs that argos upload stores as PNG under their .jpg name), colliding names get a (2) suffix, and the --json shape { build, directory, files: [{ name, url, contentType, status, path }] }.
  • Paginated lists: adds build list (--limit, 100 by default).

Security and compliance › Export your data: the feature came from the question "can I bulk export all screenshots and baselines of a project?". This section answered it with a jq + curl script over build snapshots --json. I replaced the script with a short pointer to the three commands.

🤖 Generated with Claude Code

…load`

Add the three commands to the CLI reference: listing a project's builds,
downloading a build's screenshots, and downloading the project's latest
baseline, with the project-token-only rule, the file layout and the JSON
output. Point the data export section of the security page to them
instead of the jq and curl script.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@gregberge
gregberge merged commit dd81152 into main Oct 21, 2026
2 checks passed
@gregberge
gregberge deleted the docs/cli-build-baseline-download branch October 21, 2026 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant