Browse documentation

Artifact-only Jobs

Build a Containerfile image only to extract its artifacts.

Set execution.artifact_only to true when a Containerfile's final image is only an artifact carrier and must not run. Repopack builds the exact Job source, creates a temporary container from the image without starting it, and extracts every configured artifact path.

{
  "source": "refs/heads/master",
  "execution": {
    "mode": "containerfile",
    "containerfile": "Containerfile.release",
    "context": ".",
    "artifact_only": true
  },
  "artifact_paths": ["/release"]
}

For example, the final stage can be a clean scratch image:

FROM scratch
COPY --from=build /work/release /release

Artifact-only mode is valid only for Containerfile Jobs, cannot be combined with execution.command, and requires at least one valid absolute artifact_paths entry. Omitting it or setting it to false preserves the normal build, run, then extract sequence. Image-mode Jobs cannot declare the field.

Convert an existing run-then-extract Containerfile Job with:

rp job update <job-number> --artifact-only --command.none

Both flags are required: the command removal is explicit rather than an implicit consequence of --artifact-only. Repopack applies both changes in one locked update and preserves the Containerfile, context, build-argument declarations, artifact paths, source, name, description, and other unrelated settings. The conversion may be combined atomically with --name, --source, or --description; use rp job args separately for build-argument declaration edits. The command reports the resulting execution settings. Converting an already artifact-only Job is safe and returns its unchanged effective settings. The update does not start a Run or publish a Release.

Every configured path must exist. A missing path fails the run rather than publishing an incomplete release. Cancellation, failure, or lease loss removes the extraction container, built image, and partial artifact workspace; only a successfully fenced run atomically publishes its success status, artifact manifest, and source SHA. Artifact list and download routes expose files only for succeeded Runs.