oz0 job outcome
Record how a finished job's work held up later: success or failure, under a name such as merged or closed_unmerged.
For: Operators and developers looking up a command.
Record how a finished job's work held up later: success or failure, under a name such as merged or closed_unmerged. Each name is recorded once per job, within 14 days of the job's end, and a job has at most 20. A rollout's quality gate counts the failures of a candidate's jobs against the installed version's. The audit log keeps the name and the outcome, never the detail. Needs the permission to manage jobs.
An agent records the same with the built-in tool oz.report_outcome, for jobs of its own plugin.
Usage
oz0 job outcome JOB [flags]
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--detail | string | a short note, such as a pull request's address (at most 500 characters; shown only with the content permission) | |
--json | bool | print JSON instead of a table | |
--name | string | what the result is about: lowercase letters, digits, dots, dashes and underscores, such as merged | |
--outcome | string | success or failure | |
--tenant | string | default | tenant |
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.