Staging: reduce concurrent builds from 3 to 2#51
Conversation
|
Warning Rate limit exceeded
⌛ 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. 📝 WalkthroughWalkthroughThree staging environment configuration files have been updated to reduce the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
c323f40 to
1ff7dd6
Compare
The staging1 build agents only have 4 CPUs and 4GB RAM, which is insufficient to run the Artemis Spring server plus 3 concurrent builds simultaneously. Reducing to 2 concurrent builds to prevent resource exhaustion that was causing Docker daemon freezes.
1ff7dd6 to
48adc95
Compare
Summary
Motivation
The staging build agents only have 4 CPUs and 4GB RAM, which is insufficient to run the Artemis Spring server plus 3 concurrent builds simultaneously.
This was causing Docker daemon freezes due to resource exhaustion, leading to:
Changes
artemis_staging1.yml: concurrent_build_size 3 → 2artemis_staging2.yml: concurrent_build_size 3 → 2artemis_staging_localci_nodes_buildagent.yml: concurrent_build_size 3 → 2Testing
Already applied manually to staging1 build agents and verified working via the REST API:
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.