Browse documentation

Jobs and Runs

Build evidence tied to exact source, separate from releases and deployments.

A Job describes repeatable project work against a Git source, such as building and collecting artifacts. A Run is one execution of that Job. The Run records the exact source commit and result; changing the Job later does not rewrite an earlier Run's identity.

Source and identity

Jobs have durable numbers local to their project; Runs have numbers local to their Job. For example, Job 1 / Run 2 names one execution in a particular project, not a global database record. A Job can use a manual branch, tag or full commit SHA as its source. An explicitly configured trigger:master source additionally starts Runs for accepted advances of master; a manual Run can override its source for that execution without changing the Job's durable setting. Build with a Job shows the manual path.

Artifacts from a successful Run carry names, sizes, and SHA-256 evidence; downloads recheck stored bytes against the build-time record. A Run's success is not proof that all later bytes remain available. Completed Runs are subject to per-Job retention, so a historical Run can disappear, along with its artifacts. A manual freeze protects one exact Run from ordinary retention but does not publish it or make its artifacts anonymous.

A Run is not a Release or deployment

Job artifacts require project authorization, even when a historical Job configuration once described them as public. To distribute immutable bytes publicly, an authorized actor explicitly publishes a Release from a verified successful Run. Publication holds that exact Run and its evidence, independently of a manual freeze. Revoking or deprecating a Release does not lift the hold; deleting the containing project is the outer lifecycle exception.

An App deployment selects and runs project code as a service. It is not a Job Run, and an automatic Job trigger does not imply an automatic App deployment. A rolling channel can show currently eligible successful Runs without publishing them as immutable Releases or holding them against retention.