jadpo runs

Check runs before a deploy.

Run against production before a deploy (area 12, "Deploys"): unfinished lists the unfinished runs of actions with several changing calls, and the batch runs still going, that the build named by --build changes, so they can be let finish first. The build is the checkout's, which must make the build named. A record whose action's steps the build changes stops as diverged when it runs again, one whose action no longer keeps steps would send them again, and a batch run whose call the build changes fails; the others resume. It reads no request, answer or key, and none of the app's settings beyond its connections' addresses. The databases are the ones the stores' connections' settings give, or a running jadpo dev's, or the one --url names (with --store when there are several). Times are in UTC.

jadpo runs <action>

Arguments

• action: What to list: unfinished

Flags

• --build <build id>: The build being deployed, the checkout's
• --url <url>: The database the runs are in
• --store <name>: The store --url's database is

On every command

• --json: Print data for tools instead of text
• --help: Show every flag, with examples
• --color <when>: Choose when to use colour

jadpo runs --json writes one JSON document to standard output instead of text, with the same exit code. The document has schemaVersion, command ("runs"), ok, data (what the command produced, null when it failed) and diagnostics (each error with its rule, reason, next and help). A command that needs a terminal refuses --json and names the flags that do the same job.

Examples

# See what a deploy would change, before deployingjadpo runs unfinished --build 3f9a1c2e0b7d4e5f8a6b9c0d1e2f3a4b

Errors

• cli.runs_arguments: Runs command has invalid arguments
• runs.unavailable: Unfinished runs' database couldn't be read
• toolchain.project_not_found: Project could not be found