OpenShift: CI Pipeline - zhuje/openshift-wiki GitHub Wiki

Documentation

https://docs.ci.openshift.org/docs/how-tos/onboarding-a-new-component/

Notes

Onboarding a new component for automated testing and merging

1. Prow Configurations

• See configs for openshift/release : https://github.com/openshift/release/pull/51065
• For test configs to work, you need a Dockerfile.test in the repository you are trying to target: https://github.com/openshift/troubleshooting-panel-console-plugin/blob/main/Dockerfile.test
• Run the test file to make sure the image works docker build -f Dockerfile.test .
• Open a PR in /openshift/release. Run /pj-rehearse to run Dockerfile and Dockerfile.test. Once those test pass add /pj-rehearse ack

2. Image Mirroring

• Add a new line to map to your repo. See https://github.com/openshift/release/pull/51974 . In this example, the file core-services/image-mirroring/observability-ui/mapping_observability_ui_latest_quay, add the line registry.ci.openshift.org/observability-ui/0.1:<FOO-YOUR-PLUGIN-REPO-NAME> quay.io/openshift-observability-ui/<FOO-YOUR-PLUGIN-REPO-NAME>:latest quay.io/openshift-observability-ui/<FOO-YOUR-PLUGIN-REPO-NAME>:v0.1.0 quay.io/openshift-observability-ui/<FOO-YOUR-PLUGIN-REPO-NAME>:v0.1

Note for a new repository

1. Add the new namespace in app.ci : https://github.com/openshift/release/pull/51216

• See app.ci console: https://docs.ci.openshift.org/docs/getting-started/useful-links/. The new namespace should appear once you merge the configs correctly.

2. Add infra : https://github.com/openshift/release/pull/52132