Skip cypress from the UI image building process#379
Conversation
|
The pipeline still failed due to the errors returned by the Cypress npm package link, but the tests themselves could run in the CI. |
40c8d24 to
3512ff7
Compare
|
Warning Rate limit exceeded@celdrake has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 13 minutes and 4 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📒 Files selected for processing (2)
WalkthroughThis pull request transitions the Cypress testing setup from a workspace-managed package to a direct dev dependency. The integration test scripts are updated to use a standalone Cypress installation, and Docker build context is configured to exclude the Cypress directory. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
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 |
3512ff7 to
264d67a
Compare
|
I missed adding the |
264d67a to
ac34c30
Compare
ac34c30 to
9790a78
Compare
Cypress npm is failing today, and I realized this is also happening when building the UI images.
We can skip as it's not needed and it will be faster etc.
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.