Skip to content

vcf-migration-operator config retry#79059

Open
jcpowermac wants to merge 1 commit intoopenshift:mainfrom
jcpowermac:try-again-vmo
Open

vcf-migration-operator config retry#79059
jcpowermac wants to merge 1 commit intoopenshift:mainfrom
jcpowermac:try-again-vmo

Conversation

@jcpowermac
Copy link
Copy Markdown
Contributor

@jcpowermac jcpowermac commented May 8, 2026

Summary

This PR adds CI operator configuration for the vcf-migration-operator component in the OpenShift organization. It establishes automated build and test pipelines for the project on the main branch.

Changes

The new configuration file defines:

  • Build and test automation: Configures make build as the binary build command and make test for test execution
  • Container image: Specifies that a Docker image (vcf-migration-operator) will be built from the repository's Dockerfile
  • Unit testing: Defines a unit test job that runs make test within a container sourced from the source repository
  • Resource constraints: Applies resource limits across all build/test components (4Gi memory limit, 200Mi memory request, 100m CPU request) to control cluster resource usage
  • Build configuration: Uses the repository itself as the build root, allowing the CI system to access the project's build scripts and dependencies

This establishes the automated CI pipeline for vcf-migration-operator within the OpenShift CI infrastructure, enabling continuous integration checks on the main branch.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 8, 2026

Walkthrough

A new OpenShift CI Operator configuration file is added for the openshift-vcf-migration-operator project, specifying build commands, Docker image configuration, resource limits, unit test execution, and metadata identifiers.

Changes

CI Configuration for VCF Migration Operator

Layer / File(s) Summary
Build & Image Configuration
ci-operator/config/openshift/vcf-migration-operator/openshift-vcf-migration-operator-main.yaml (lines 1–15)
Build root sourced from repository; binary build via make build; Docker image built from Dockerfile and tagged as vcf-migration-operator.
Resource Constraints
ci-operator/config/openshift/vcf-migration-operator/openshift-vcf-migration-operator-main.yaml (lines 1–15)
Resource requests and limits applied to all components: 4Gi memory limit, 200Mi memory request, 100m CPU request.
Test Configuration
ci-operator/config/openshift/vcf-migration-operator/openshift-vcf-migration-operator-main.yaml (lines 16–20)
Unit tests configured to run make test in a container sourced from src.
Metadata
ci-operator/config/openshift/vcf-migration-operator/openshift-vcf-migration-operator-main.yaml (lines 21–24)
Generated metadata section identifies branch main, organization openshift, and repository vcf-migration-operator.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 12
✅ Passed checks (12 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'vcf-migration-operator config retry' accurately describes the main change: adding a new CI configuration for the vcf-migration-operator after a previous attempt.
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 The PR only adds OpenShift CI configuration (YAML), not Ginkgo test code. No test name definitions exist in the added file, making the check not applicable.
Test Structure And Quality ✅ Passed This PR contains no Ginkgo tests. It adds CI configuration files and standard Go unit tests (testing.T), which are outside the scope of this Ginkgo-specific check.
Microshift Test Compatibility ✅ Passed The PR adds CI configuration files (YAML) only, not Ginkgo e2e tests. The custom check is not applicable when no Ginkgo test code is added.
Single Node Openshift (Sno) Test Compatibility ✅ Passed No Ginkgo e2e tests added. PR only adds CI operator configuration YAML file with build/test commands and metadata. The SNO compatibility check is not applicable.
Topology-Aware Scheduling Compatibility ✅ Passed This PR adds only a CI Operator configuration file with no deployment manifests, operator code, or runtime scheduling constraints. CI configs do not affect cluster topology compatibility.
Ote Binary Stdout Contract ✅ Passed The OTE Binary Stdout Contract check applies to Go test code. This PR only adds CI/Prow configuration YAML files with no source code, test code, or executables. Check is not applicable.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed PR adds only CI Operator configuration file for vcf-migration-operator, not actual Ginkgo e2e test code. Check is not applicable.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot requested review from Prucek and smg247 May 8, 2026 18:15
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 8, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jcpowermac

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 8, 2026
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@jcpowermac: 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-vcf-migration-operator-main-images openshift/vcf-migration-operator presubmit Presubmit changed
pull-ci-openshift-vcf-migration-operator-main-unit openshift/vcf-migration-operator presubmit Presubmit changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

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.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
ci-operator/config/openshift/vcf-migration-operator/openshift-vcf-migration-operator-main.yaml (1)

15-20: ⚡ Quick win

Remove unused test_binary_build_commands to avoid redundant test artifact builds.

At Line 15, test_binary_build_commands: make test builds test binaries into pipeline:test-bin, but the unit test runs from container.from: src and does not consume them. Since the same make test command runs directly in the test container, the pre-build step is redundant.

Suggested fix
- test_binary_build_commands: make test
 tests:
 - as: unit
   commands: make test
   container:
     from: src
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/openshift/vcf-migration-operator/openshift-vcf-migration-operator-main.yaml`
around lines 15 - 20, Remove the unused pre-build key test_binary_build_commands
(the line "test_binary_build_commands: make test") since unit tests run inside
the test container (tests -> as: unit, container.from: src) and the same make
test is executed there; delete that key from the YAML and ensure no other
pipeline steps reference test_binary_build_commands.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In
`@ci-operator/config/openshift/vcf-migration-operator/openshift-vcf-migration-operator-main.yaml`:
- Around line 15-20: Remove the unused pre-build key test_binary_build_commands
(the line "test_binary_build_commands: make test") since unit tests run inside
the test container (tests -> as: unit, container.from: src) and the same make
test is executed there; delete that key from the YAML and ensure no other
pipeline steps reference test_binary_build_commands.

ℹ️ Review info
⚙️ Run configuration

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

Review profile: CHILL

Plan: Enterprise

Run ID: a1edac01-c322-4ce6-bc2b-f1cabfcf2262

📥 Commits

Reviewing files that changed from the base of the PR and between 3cc5bfb and 28a630f.

⛔ Files ignored due to path filters (1)
  • ci-operator/jobs/openshift/vcf-migration-operator/openshift-vcf-migration-operator-main-presubmits.yaml is excluded by !ci-operator/jobs/**
📒 Files selected for processing (1)
  • ci-operator/config/openshift/vcf-migration-operator/openshift-vcf-migration-operator-main.yaml

@jcpowermac
Copy link
Copy Markdown
Contributor Author

/test pull-ci-openshift-vcf-migration-operator-main-images pull-ci-openshift-vcf-migration-operator-main-unit

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 8, 2026

@jcpowermac: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test app-ci-config-dry
/test boskos-config
/test boskos-config-generation
/test build03-dry
/test build04-dry
/test build05-dry
/test build06-dry
/test build07-dry
/test build08-dry
/test build09-dry
/test build10-dry
/test build11-dry
/test check-gh-automation
/test check-gh-automation-tide
/test check-trigger-trusted-apps
/test ci-operator-config
/test ci-operator-config-metadata
/test ci-operator-registry
/test ci-secret-bootstrap-config-validation
/test ci-testgrid-allow-list
/test clusterimageset-validate
/test config
/test core-ci-config-dry
/test core-valid
/test generated-config
/test generated-dashboards
/test hosted-mgmt-dry
/test image-mirroring-config-validation
/test jira-lifecycle-config
/test labels
/test openshift-image-mirror-mappings
/test ordered-prow-config
/test owners
/test pr-reminder-config
/test prow-config
/test prow-config-filenames
/test prow-config-semantics
/test pylint
/test release-config
/test release-controller-config
/test rover-groups-config-validation
/test secret-generator-config-valid
/test services-valid
/test stackrox-stackrox-stackrox-stackrox-check
/test step-registry-metadata
/test step-registry-shellcheck
/test sync-rover-groups
/test verified-config
/test vsphere02-dry
/test yamllint

The following commands are available to trigger optional jobs:

/test check-cluster-profiles-config

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-release-check-gh-automation
pull-ci-openshift-release-main-ci-operator-config
pull-ci-openshift-release-main-ci-operator-config-metadata
pull-ci-openshift-release-main-ci-operator-registry
pull-ci-openshift-release-main-config
pull-ci-openshift-release-main-core-valid
pull-ci-openshift-release-main-generated-config
pull-ci-openshift-release-main-ordered-prow-config
pull-ci-openshift-release-main-owners
pull-ci-openshift-release-main-prow-config-filenames
pull-ci-openshift-release-main-prow-config-semantics
pull-ci-openshift-release-main-release-controller-config
pull-ci-openshift-release-openshift-image-mirror-mappings
pull-ci-openshift-release-yamllint
Details

In response to this:

/test pull-ci-openshift-vcf-migration-operator-main-images pull-ci-openshift-vcf-migration-operator-main-unit

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.

@jcpowermac
Copy link
Copy Markdown
Contributor Author

/pj-rehearse pull-ci-openshift-vcf-migration-operator-main-images pull-ci-openshift-vcf-migration-operator-main-unit

@openshift-merge-bot
Copy link
Copy Markdown
Contributor

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

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 8, 2026

@jcpowermac: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/owners 28a630f link true /test owners

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant