Skip to content

CI Pipeline Configuration

Use this page when adding or changing CI jobs. For test authoring and selection in existing jobs, follow Writing V2 Tests. For execution and process boundaries, see Test Flow.

Repository ownership

openshift/hypershift owns the tests, platform configuration, lifecycle orchestration, and test image definition. openshift/release owns the CI jobs and step registry that consume that image.

Use the current source for implementation details:

For registry conventions and workflow, chain, and ref definitions, follow the OpenShift CI step registry documentation.

Add or change a job

  1. Identify whether the change concerns test selection or CI infrastructure. Follow the authoring guide for labels, cluster prerequisites, and plans. Adding coverage to an existing selection does not require a release repository change.
  2. If platform or framework work is needed, agree on the approach through the advance discussion procedure, then implement it in HyperShift using the current interfaces above.
  3. In the release repository, reuse an appropriate workflow and its existing steps where possible. Add or update registry components when the job needs different infrastructure. Ensure the steps receive the required images, credentials, and configuration. For Azure diagnostic access, see worker diagnostic prerequisites.
  4. Add or update the job under ci-operator/config/openshift/hypershift/. Review triggers, change filters, image dependencies, and timeouts against the intended coverage. Use current neighboring jobs as examples instead of copying an old configuration fragment.
  5. From the release repository root, run make jobs WHAT=openshift/hypershift and the applicable repository validation. Review generated changes and submit the release PR with references to any corresponding HyperShift changes.

Validate that the resulting job selects and exercises the intended coverage; use Verify and debug to inspect its results.