Core Components on Prow

Crier

Mon, 01 Jan 0001 00:00:00 +0000

Crier reports your prowjobs on their status changes.

Usage / How to enable existing available reporters

For any reporter you want to use, you need to mount your prow configs and specify --config-path and job-config-path flag as most of other prow controllers do.

Gerrit reporter

You can enable gerrit reporter in crier by specifying --gerrit-workers=n flag.

Similar to the gerrit adapter, you’ll need to specify --gerrit-projects for your gerrit projects, and also --cookiefile for the gerrit auth token (leave it unset for anonymous).

Hook

Mon, 01 Jan 0001 00:00:00 +0000

This is a placeholder page. Some contents needs to be filled.

Horologium

Mon, 01 Jan 0001 00:00:00 +0000

This is a placeholder page. Some contents needs to be filled.

Prow-Controller-Manager

Mon, 01 Jan 0001 00:00:00 +0000

prow-controller-manager manages the job execution and lifecycle for jobs running in k8s.

It currently acts as a replacement for Plank.

It is intended to eventually replace other components, such as Sinker and Crier. See the tracking issue #17024 for details.

Advantages

Eventbased rather than cronbased, hence reacting much faster to changes in prowjobs or pods
Per-Prowjob retrying, meaning genuinely broken prowjobs will not be retried forever and transient errors will be retried much quicker
Uses a cache for the build cluster rather than doing a LIST every 30 seconds, reducing the load on the build clusters api server

Exclusion with other components

This is mutually exclusive with only Plank. Only one of them may have more than zero replicas at the same time.

Sinker

Mon, 01 Jan 0001 00:00:00 +0000

This is a placeholder page. Some contents needs to be filled.