Browse documentation

Retain Job Runs

Understand Run retention, freezing, and immutable Release holds.

Job Runs are not all kept forever. For each Job, Repopack protects manually frozen and Release-held completed Runs, its latest successful completed Run, and the newest 19 other completed Runs. Queued and running Runs are not retention candidates. This is a count policy, not a storage or byte quota; an idle Job may retain a backlog until a later Run triggers cleanup.

Freeze evidence deliberately

rp job freeze <job-number> <run-number>
rp job unfreeze <job-number> <run-number>

Both operations require job.manage and browser confirmation. Freezing retains that exact Run's record, log, artifacts and remaining workspace outside ordinary count retention; it does not publish its artifacts or freeze future Runs. Unfreezing returns it to normal retention and may remove it immediately. A Job with frozen Runs cannot be deleted normally. Before a download, verify that the Run still exists; once retention removes an ordinary Run, its history and artifact URLs are gone rather than replaced by an expired stub.

Understand Release holds

A published immutable Release creates a separate hold on its verified successful Run and artifact evidence. Unfreezing a manual freeze does not lift that hold; deprecating or revoking the Release does not lift it either. Whole-project deletion is the explicit exception to retention. A rolling channel's temporary eligible Run view does not create a Release hold. Release distribution explains why a frozen Run is not a public version, and publish a Release covers the intentional publication boundary.

rp job purge <job-number> is a different, guarded maintenance action: it can remove ordinary completed Runs after confirmation of an exact plan, but never protected or active Runs. Do not use it as a substitute for ordinary retention or freeze. See the Job CLI reference for the command family.