OTA-1896: Add a configuration for the openshift/cluster-update-console-plugin repository#77093
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@DavidHurta: This pull request references OTA-1896 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn response to this: 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. |
openshift-ci
Bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
openshift-ci
Bot
added
the
approved
|
/test all |
|
/label tide/merge-method-squash |
openshift-ci
Bot
added
the
tide/merge-method-squash
|
/pj-rehearse pull-ci-openshift-cluster-update-console-plugin-main-build pull-ci-openshift-cluster-update-console-plugin-main-frontend pull-ci-openshift-cluster-update-console-plugin-main-e2e |
|
@DavidHurta: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-cluster-update-console-plugin-main-frontend pull-ci-openshift-cluster-update-console-plugin-main-e2e |
|
@DavidHurta: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/test all |
DavidHurta
force-pushed
the
new-repo-openshift-cluster-update-console-plugin
branch
from
673c0af to
de534c7
Compare
|
/pj-rehearse pull-ci-openshift-cluster-update-console-plugin-main-e2e |
|
@DavidHurta: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Generated by running `make new-repo` and interactively providing options. Manually added additional required labels: verified and jira/valid-reference For the source image utilize the .ci-operator.yaml file in the respective repository [1]. Modified the config with minor modifications, run `make update`. Introduce a one test with an existing script in the repository. The test-prow-e2e.sh script for an e2e verification requires additional modifications in the plugin repository to be run in CI. Follow-up PRs will introduce more presubmit tests. [1] https://docs.ci.openshift.org/architecture/ci-operator/#build-root-image
The initial OWNERS files needs to be added manually [1]. > Shortly following the merge of the onboarding PR, the periodic-prow-auto-owners job will sync the OWNERS file from the component repository to the relevant directories. [1] [1] https://docs.ci.openshift.org/how-tos/onboarding-a-new-component/#setting-up-team-ownership-of-ci-operator-and-prow-config-files
DavidHurta
force-pushed
the
new-repo-openshift-cluster-update-console-plugin
branch
from
de534c7 to
b952f94
Compare
|
/test all |
|
/pj-rehearse pull-ci-openshift-cluster-update-console-plugin-main-frontend |
|
@DavidHurta: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/unlabel tide/merge-method-squash |
|
/remove-label tide/merge-method-squash |
openshift-ci
Bot
removed
the
tide/merge-method-squash
|
@DavidHurta: This pull request references OTA-1896 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
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. |
|
@DavidHurta: This pull request references OTA-1896 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.22.0" version, but no target version was set. DetailsIn response to this:
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. |
|
@DavidHurta: This pull request references OTA-1896 which is a valid jira issue. DetailsIn response to this:
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. |
openshift-ci
Bot
removed
the
do-not-merge/work-in-progress
|
/cc @wking |
|
/pj-rehearse ack |
|
@DavidHurta: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci-robot
added
the
rehearsals-ack
|
@DavidHurta: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
/retest-required |
| - fao89 | ||
| - hongkailiu | ||
| - pratikmahajan | ||
| - wking |
There was a problem hiding this comment.
nit: Instead of hard-coding again locally here, maybe we can update the cincinnati-approvers alias and then use it in all of these locations?
| - fao89 | ||
| - hongkailiu | ||
| - pratikmahajan | ||
| - wking |
There was a problem hiding this comment.
Nevermind, I see from your b952f94 commit message that we don't actually care what goes in as seed data here.
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DavidHurta, wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@DavidHurta: Updated the following 3 configmaps:
DetailsIn response to this:
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. |
…ectory Based on similar content for the similarly-new cluster-update-console-plugin repository which landed in e87d744b63 (OTA-1896: Add a configuration for the openshift/cluster-update-console-plugin repository, 2026-04-07, openshift#77093), but with the appropriate repo name (agentic-skills) and the current agentic-skills root owner/approvers.
…ectory Based on similar content for the similarly-new cluster-update-console-plugin repository which landed in de87d74 (OTA-1896: Add a configuration for the openshift/cluster-update-console-plugin repository, 2026-04-07, openshift#77093), but with the appropriate repo name (agentic-skills) and the current agentic-skills root owner/approvers.
…ectory Based on similar content for the similarly-new cluster-update-console-plugin repository which landed in de87d74 (OTA-1896: Add a configuration for the openshift/cluster-update-console-plugin repository, 2026-04-07, openshift#77093), but with the appropriate repo name (agentic-skills) and the current agentic-skills root owner/approvers.
…ectory (#78069) Based on similar content for the similarly-new cluster-update-console-plugin repository which landed in de87d74 (OTA-1896: Add a configuration for the openshift/cluster-update-console-plugin repository, 2026-04-07, #77093), but with the appropriate repo name (agentic-skills) and the current agentic-skills root owner/approvers.
…e-plugin repository (openshift#77093) * release: Add openshift/cluster-update-console-plugin repository Generated by running `make new-repo` and interactively providing options. Manually added additional required labels: verified and jira/valid-reference For the source image utilize the .ci-operator.yaml file in the respective repository [1]. Modified the config with minor modifications, run `make update`. Introduce a one test with an existing script in the repository. The test-prow-e2e.sh script for an e2e verification requires additional modifications in the plugin repository to be run in CI. Follow-up PRs will introduce more presubmit tests. [1] https://docs.ci.openshift.org/architecture/ci-operator/#build-root-image * cluster-update-console-plugin: Add OWNERS files The initial OWNERS files needs to be added manually [1]. > Shortly following the merge of the onboarding PR, the periodic-prow-auto-owners job will sync the OWNERS file from the component repository to the relevant directories. [1] [1] https://docs.ci.openshift.org/how-tos/onboarding-a-new-component/#setting-up-team-ownership-of-ci-operator-and-prow-config-files
…ectory (openshift#78069) Based on similar content for the similarly-new cluster-update-console-plugin repository which landed in de87d74 (OTA-1896: Add a configuration for the openshift/cluster-update-console-plugin repository, 2026-04-07, openshift#77093), but with the appropriate repo name (agentic-skills) and the current agentic-skills root owner/approvers.
…ectory (openshift#78069) Based on similar content for the similarly-new cluster-update-console-plugin repository which landed in de87d74 (OTA-1896: Add a configuration for the openshift/cluster-update-console-plugin repository, 2026-04-07, openshift#77093), but with the appropriate repo name (agentic-skills) and the current agentic-skills root owner/approvers.
3 participants
Add a Prow configuration for the new openshift/cluster-update-console-plugin repository.
Onboarding a New Component for Testing and Merge Automation Documentation: https://docs.ci.openshift.org/how-tos/onboarding-a-new-component/