ci: 接入中央复用工作流 maven-ci (@v1, 非NMS) - #2
Conversation
|
Warning Review limit reached
More reviews will be available in 32 minutes and 4 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
把 CI 接到中央的 UltiKits/ci-workflows 复用工作流上,走非 NMS 校验那条路(needs-nms: false)。这样每次 push/PR 都会在 JDK 17 和 21 两个矩阵上跑 mvn test + package,之前只有 publish.yml 在 JDK 8 上跳过测试打包,等于测试从来没在 CI 跑过。pin 的是浮动大版本 @v1,以后安全/运行时 re-pin 会自动跟上。只加了一个文件 .github/workflows/maven-ci.yml,publish.yml 没动。