[WIP] TRT-2741: Add verify-migrations presubmit for openshift/sippy#81301
[WIP] TRT-2741: Add verify-migrations presubmit for openshift/sippy#81301mstaeble wants to merge 1 commit into
Conversation
|
Skipping CI for Draft Pull Request. |
|
@mstaeble: This pull request references TRT-2741 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 "5.0.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. |
|
Tip For best results, initiate chat on the files or code changes. This comment is an automated notice from |
|
@coderabbitai review |
✅ Action performedReview finished.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughAdds a new ChangesCI Configuration Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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.
Inline comments:
In `@ci-operator/config/openshift/sippy/openshift-sippy-main.yaml`:
- Around line 50-54: The new verify-migrations job has been added to the
ci-operator config, but the generated Prow job definitions are not updated yet.
Regenerate the ci-operator jobs so
`pull-ci-openshift-sippy-main-verify-migrations` is emitted, and commit the
resulting changes in the generated jobs alongside the existing
`verify-migrations` config entry.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository YAML (base), Central YAML (inherited)
Review profile: CHILL
Plan: Enterprise
Run ID: dcf0b88d-e17d-47a6-b0c5-3a88a8bd0771
📒 Files selected for processing (1)
ci-operator/config/openshift/sippy/openshift-sippy-main.yaml
Run `make verify-migrations` on PRs that touch migration files. This checks the migration manifest for sequential numbering, no duplicates, and matching up/down SQL files. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
aecc79c to
120b6c6
Compare
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mstaeble The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Summary
verify-migrationspresubmit job foropenshift/sippythat runsmake verify-migrationspkg/db/migrations/verify-migrationstarget checks a migration manifest for sequential numbering, no duplicate versions, and matching up/down SQL files🤖 Generated with Claude Code
Summary by CodeRabbit
This update adds a new
verify-migrationspresubmit step to the OpenShift CI configuration foropenshift/sippy(ci-operator/config/openshift/sippy/openshift-sippy-main.yaml). It runsHOME=/tmp make verify-migrationsin thesrccontainer and is only triggered when a PR modifies files underpkg/db/migrations/, so migration validation happens automatically at review time.In practice, this helps prevent bad migration manifests from merging by checking that migration versions are sequential, that versions aren’t duplicated, and that each migration has matching
up/downSQL files.