NO-JIRA: Add openshift-eng/org-context CI config by jkyros · Pull Request #81295 · openshift/release

jkyros · 2026-06-30T20:49:59Z

This just adds the initial CI setup for the default github context location in org-context. It's not going to build anything, it's just a "document repository".

Summary by CodeRabbit

This PR bootstraps OpenShift CI/operator + Prow/Tide configuration for the openshift-eng/org-context repository (covering the main branch), wiring it into standard OpenShift GitHub automation and merge gating.

In practical terms, it:

Adds a new ci-operator configuration for openshift-eng/org-context (openshift-eng-org-context-main.yaml) that:
- Sets build_root to use repository-based provisioning (from_repository: true)
- Enables prowgen exposure while keeping it private (expose: true, private: true)
- Applies default resource policy for all items ('*') with requests (100m CPU, 200Mi memory) and limit (4Gi memory)
- Defines a unit test that runs make test in the src container
- Records generated metadata for main under openshift-eng/org-context
Configures repo-scoped Prow behavior for openshift-eng/org-context (_pluginconfig.yaml) by:
- Disabling self-approval for approve
- Allowing lgtm to act as LGTM (review_acts_as_lgtm: true)
- Defining the explicit set of enabled plugins for the repo
- Adding external webhook-style plugins (refresh, cherrypick, needs-rebase, jira-lifecycle-plugin) mapped to configured endpoints and relevant events
- Trusting openshift-merge-bot for merge trigger eligibility
Sets Tide merge criteria for the repo (_prowconfig.yaml) to allow merges only when approved and lgtm labels are present and specific missingLabels are absent (e.g., hold/WIP/rebase/invalid bug and invalid owners constraints).
Adds/updates the auto-generated OWNERS file for openshift-eng/org-context with approvers/reviewers jkyros and coachskyros.

openshift-ci-robot · 2026-06-30T20:50:03Z

@jkyros: This pull request explicitly references no jira issue.

Details

In response to this:

This just adds the initial CI setup for the default github context location in org-context. It's not going to build anything, it's just a "document repository".

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

coderabbitai · 2026-06-30T20:50:26Z

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: f7481064-1e89-4ae2-b397-99709db97e03

📥 Commits

Reviewing files that changed from the base of the PR and between d493992 and c4f04a8.

⛔ Files ignored due to path filters (2)

ci-operator/jobs/openshift-eng/org-context/OWNERS is excluded by !ci-operator/jobs/**
ci-operator/jobs/openshift-eng/org-context/openshift-eng-org-context-main-presubmits.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (4)

ci-operator/config/openshift-eng/org-context/OWNERS
ci-operator/config/openshift-eng/org-context/openshift-eng-org-context-main.yaml
core-services/prow/02_config/openshift-eng/org-context/_pluginconfig.yaml
core-services/prow/02_config/openshift-eng/org-context/_prowconfig.yaml

✅ Files skipped from review due to trivial changes (1)

ci-operator/config/openshift-eng/org-context/OWNERS

🚧 Files skipped from review as they are similar to previous changes (2)

core-services/prow/02_config/openshift-eng/org-context/_prowconfig.yaml
core-services/prow/02_config/openshift-eng/org-context/_pluginconfig.yaml

Walkthrough

This PR adds CI-operator, OWNERS, Prow plugin, and Tide configuration for openshift-eng/org-context, including a build root, unit test job, plugin enablement, external plugin wiring, trusted trigger settings, and merge-label requirements.

Changes

Repository CI onboarding

Layer / File(s)	Summary
CI operator and ownership metadata `ci-operator/config/openshift-eng/org-context/OWNERS`, `ci-operator/config/openshift-eng/org-context/openshift-eng-org-context-main.yaml`	Adds generated ownership metadata and a CI-operator config with `build_root`, resource requests/limits, a `make test` unit job, and generated repository metadata.
Prow plugin and Tide rules `core-services/prow/02_config/openshift-eng/org-context/_pluginconfig.yaml`, `core-services/prow/02_config/openshift-eng/org-context/_prowconfig.yaml`	Adds repo-scoped approve and lgtm settings, enables the repo plugin set, wires external webhook-style plugins, configures trusted trigger apps, and defines Tide query and missing-label rules.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

openshift/release#81271: Also adds Prow/Tide onboarding-style configuration for a repository, including plugin wiring and merge-gating rules.

Suggested labels: lgtm, rehearsals-ack

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: adding CI config for openshift-eng/org-context.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	Only CI/prow YAML and OWNERS files changed; no Ginkgo test code or titles were added or edited.
Test Structure And Quality	✅ Passed	PASS: The PR only adds YAML CI/prow config; no Ginkgo test files or test code were added or modified, so this checklist is not applicable.
Microshift Test Compatibility	✅ Passed	Only CI/prow YAML and OWNERS files changed; no new Ginkgo e2e tests or MicroShift-unsafe API usage were added.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	No new Ginkgo e2e tests were added; the PR only changes CI/Prow YAML and OWNERS config, so SNO test compatibility isn’t implicated.
Topology-Aware Scheduling Compatibility	✅ Passed	Only CI/Prow config changed; no deployment manifests, controllers, or scheduling constraints were added.
Ote Binary Stdout Contract	✅ Passed	Diff only adds CI/Prow YAML and OWNERS metadata; no process-level code or stdout writes were changed.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No new Ginkgo/e2e tests were added; only CI/prow YAML and OWNERS files. I found no IPv4 literals or public-internet connectivity requirements in the changed files.
No-Weak-Crypto	✅ Passed	Touched files are only CI/Prow YAML and OWNERS metadata; no MD5/SHA1/DES/RC4/3DES/Blowfish/ECB, custom crypto, or secret comparisons were present.
Container-Privileges	✅ Passed	The added org-context CI/Prow YAMLs contain no privileged, hostPID/Network/IPC, SYS_ADMIN, root, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	PASS: Touched files are YAML configs only; scans found no log/debug statements or secret-like literals, just plugin endpoints and CI config.

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

_{Comment @coderabbitai help to get the list of available commands.}

jkyros · 2026-06-30T20:54:57Z

/pj-rehearse pull-ci-openshift-eng-org-context-main-unit

openshift-merge-bot · 2026-06-30T20:55:00Z

@jkyros: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

jkyros · 2026-07-01T00:01:58Z

hmm has it taken effect yet?
/verify-owners

jkyros · 2026-07-01T00:02:57Z

/pj-rehearse pull-ci-openshift-eng-org-context-main-unit

openshift-merge-bot · 2026-07-01T00:03:00Z

@jkyros: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

jkyros · 2026-07-01T03:05:47Z

/verify-owners

jkyros · 2026-07-01T03:38:15Z

hmm I think I need to add the openshift bots to the org-context repo since it's not totally public

jkyros · 2026-07-01T16:46:35Z

/pj-rehearse pull-ci-openshift-eng-org-context-main-unit

jkyros · 2026-07-01T16:46:43Z

/verify-owners

openshift-merge-bot · 2026-07-01T16:46:48Z

@jkyros: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

jkyros · 2026-07-01T18:49:17Z

/pj-rehearse pull-ci-openshift-eng-org-context-main-unit

openshift-merge-bot · 2026-07-01T18:49:20Z

@jkyros: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

This just adds the initial CI setup for the default github context location in org-context. There aren't really any tests yet, I really just want the bots to work and merge, etc. Signed-off-by: John Kyros <jkyros@redhat.com>

jkyros · 2026-07-01T19:23:54Z

/pj-rehearse pull-ci-openshift-eng-org-context-main-unit

openshift-merge-bot · 2026-07-01T19:23:57Z

@jkyros: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

openshift-merge-bot · 2026-07-01T19:25:21Z

[REHEARSALNOTIFIER]
@jkyros: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-openshift-eng-org-context-main-unit	openshift-eng/org-context	presubmit	Presubmit changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

jkyros · 2026-07-01T19:27:09Z

/pj-rehearse pull-ci-openshift-eng-org-context-main-unit

openshift-merge-bot · 2026-07-01T19:27:14Z

@jkyros: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

openshift-ci · 2026-07-01T19:41:56Z

@jkyros: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

hoxhaeris · 2026-07-01T19:50:40Z

/lgtm

openshift-ci · 2026-07-01T19:51:48Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hoxhaeris, jkyros

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

jkyros · 2026-07-01T19:53:04Z

/pj-rehearse ack

openshift-merge-bot · 2026-07-01T19:54:05Z

@jkyros: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

openshift-ci · 2026-07-01T19:59:51Z

@jkyros: Updated the following 2 configmaps:

config configmap in namespace ci at cluster app.ci using the following files:
- key core-services-prow-02_config-openshift-eng-org-context-_prowconfig.yaml using file core-services/prow/02_config/openshift-eng/org-context/_prowconfig.yaml
config configmap in namespace ci at cluster core-ci using the following files:
- key core-services-prow-02_config-openshift-eng-org-context-_prowconfig.yaml using file core-services/prow/02_config/openshift-eng/org-context/_prowconfig.yaml

Details

In response to this:

This just adds the initial CI setup for the default github context location in org-context. It's not going to build anything, it's just a "document repository".

Summary by CodeRabbit

This PR bootstraps OpenShift CI/operator + Prow/Tide configuration for the openshift-eng/org-context repository (covering the main branch), wiring it into standard OpenShift GitHub automation and merge gating.

In practical terms, it:

Adds a new ci-operator configuration for openshift-eng/org-context (openshift-eng-org-context-main.yaml) that:

Sets build_root to use repository-based provisioning (from_repository: true)

Enables prowgen exposure while keeping it private (expose: true, private: true)

Applies default resource policy for all items ('*') with requests (100m CPU, 200Mi memory) and limit (4Gi memory)

Defines a unit test that runs make test in the src container

Records generated metadata for main under openshift-eng/org-context

Configures repo-scoped Prow behavior for openshift-eng/org-context (_pluginconfig.yaml) by:

Disabling self-approval for approve

Allowing lgtm to act as LGTM (review_acts_as_lgtm: true)

Defining the explicit set of enabled plugins for the repo

Adding external webhook-style plugins (refresh, cherrypick, needs-rebase, jira-lifecycle-plugin) mapped to configured endpoints and relevant events

Trusting openshift-merge-bot for merge trigger eligibility

Sets Tide merge criteria for the repo (_prowconfig.yaml) to allow merges only when approved and lgtm labels are present and specific missingLabels are absent (e.g., hold/WIP/rebase/invalid bug and invalid owners constraints).

Adds/updates the auto-generated OWNERS file for openshift-eng/org-context with approvers/reviewers jkyros and coachskyros.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

This just adds the initial CI setup for the default github context location in org-context. There aren't really any tests yet, I really just want the bots to work and merge, etc. Signed-off-by: John Kyros <jkyros@redhat.com>

openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 30, 2026

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 30, 2026

openshift-ci Bot requested review from bear-redhat and danilo-gemoli June 30, 2026 20:51

jkyros force-pushed the add-org-context branch from ea7167b to d493992 Compare June 30, 2026 23:26

openshift-ci Bot added the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Jun 30, 2026

openshift-ci Bot removed the do-not-merge/invalid-owners-file Indicates that a PR should not merge because it has an invalid OWNERS file in it. label Jul 1, 2026

Add openshift-eng/org-context CI config

c4f04a8

This just adds the initial CI setup for the default github context location in org-context. There aren't really any tests yet, I really just want the bots to work and merge, etc. Signed-off-by: John Kyros <jkyros@redhat.com>

jkyros force-pushed the add-org-context branch from d493992 to c4f04a8 Compare July 1, 2026 19:22

openshift-ci Bot assigned hoxhaeris Jul 1, 2026

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jul 1, 2026

openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Jul 1, 2026

openshift-merge-bot Bot merged commit 7830985 into openshift:main Jul 1, 2026
21 checks passed

Uh oh!

Conversation

jkyros commented Jun 30, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

openshift-ci-robot commented Jun 30, 2026

Uh oh!

coderabbitai Bot commented Jun 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Uh oh!

jkyros commented Jun 30, 2026

Uh oh!

openshift-merge-bot Bot commented Jun 30, 2026

Uh oh!

jkyros commented Jul 1, 2026

Uh oh!

jkyros commented Jul 1, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 1, 2026

Uh oh!

jkyros commented Jul 1, 2026

Uh oh!

jkyros commented Jul 1, 2026

Uh oh!

jkyros commented Jul 1, 2026

Uh oh!

jkyros commented Jul 1, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 1, 2026

Uh oh!

jkyros commented Jul 1, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 1, 2026

Uh oh!

jkyros commented Jul 1, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 1, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 1, 2026

Uh oh!

jkyros commented Jul 1, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 1, 2026

Uh oh!

openshift-ci Bot commented Jul 1, 2026

Uh oh!

hoxhaeris commented Jul 1, 2026

Uh oh!

openshift-ci Bot commented Jul 1, 2026

Uh oh!

jkyros commented Jul 1, 2026

Uh oh!

openshift-merge-bot Bot commented Jul 1, 2026

Uh oh!

Uh oh!

openshift-ci Bot commented Jul 1, 2026

Summary by CodeRabbit

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

jkyros commented Jun 30, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented Jun 30, 2026 •

edited

Loading