Browse documentation

Job and Run numbers

Use project-local Job and Job-local Run identities and inspect artifacts.

Jobs use immutable project-local numbers. The first Job in each project is Job 1, independent of Jobs created elsewhere. Runs already use immutable numbers local to their Job, so Job 1 / Run 2 is addressed consistently:

rp job show 1
rp job runs 1
rp job log 1 2
rp job artifacts 1 2 --output ./release

Browser and API routes use the same numbers, scoped by project:

/project/example/jobs/1
/api/v0/projects/example/jobs/1/runs/2

Database id, job_id, and project_id values are internal implementation details and are omitted from public Job and Run JSON. Numeric Job and Run arguments are always local numbers, not global database IDs.

Job numbers are allocated atomically and monotonically within each project. Deleting a Job does not make its number available for reuse. Run numbers and associations do not change when a Job is edited.

Job names are nonempty and unique within their project, but unlike Job numbers they may be changed. Use rp job update <job-number> --name <new-name>; the command may be combined with --source and --description, and only supplied fields change. Renaming to the current name succeeds. A name already held by another Job in the project is refused, while another project may use the same name.

Completed Run retention is also per Job: Repopack keeps every frozen or Release-held completed Run, the latest successful Run, and 19 other newest completed Runs. rp job freeze <job> <run> protects one exact Run without freezing its Job or changing artifact access; rp job unfreeze <job> <run> resumes ordinary retention unless an independent Release hold remains. See Job Run retention.

Browser artifact previews

The Run history keeps the artifact download action, filename, checksum tooltip, and size visible. JSON, Markdown, and bounded UTF-8 .txt, .text, and .log artifacts also have a View button that loads an inline preview on demand. Only one preview is open at a time, and collapsing its Run closes it.

JSON is validated and pretty-printed. Markdown uses Repopack's safe Markdown renderer, and plain text is escaped. Unsupported, malformed, binary, missing, or files over 256 KiB remain downloadable but are not rendered inline. Preview reads require job.read, including for Runs that historically snapshotted public artifact access. Anonymous distribution uses public Release URLs.

Listings, downloads, and previews use the name, size, and SHA-256 captured in the successful Run manifest. Bytes are verified before any response is served; changed or missing bytes are rejected. Historical Runs without complete build-time evidence are not re-hashed from present storage. See Job Run artifact integrity.