ProwJob

ProwJob is a Kubernetes Custom Resource used by Prow, a CI system originally developed for Kubernetes' test infrastructure. A ProwJob represents a single execution of a Prow job, such as a presubmit, postsubmit, periodic, or batch test, and serves as the central record of that run from creation to completion.

The ProwJob spec describes how the job should be executed. Key fields typically include the type of job (presubmit, postsubmit, periodic, or batch), the job name as configured in Prow, the agent that will run the job (for example kubernetes or Jenkins), and references (refs) to the repository and pull requests involved. Decoration configuration may be present to control how the job is run inside a Pod, including log streaming and artifact handling. Other fields can include rerun commands, context naming, and scheduling details for periodic and batch jobs.

The status portion of a ProwJob records the lifecycle and results of the run. Common status states include triggered, pending, success, failure, and error. Additional status fields typically capture the start and completion times, a URL to the job’s logs or results, and the name of the pod or Jenkins instance executing the job. When a job finishes, the ProwJob is updated with its final state and related metadata.

Lifecycle and execution flow involve Prow creating a ProwJob in response to events such as a new pull request, changes to a PR, a scheduled time for a periodic job, or a batch trigger. The Prow controller then runs the job in the configured agent, updates the status as it progresses, and stores results for visibility in GitHub status checks and the Prow dashboards.

Observability and scope: ProwJob resources enable tracking, auditing, and re-running of individual test runs, and they are integral to coordinating how Prow tests are applied to code changes in supported repositories.