Skip to content

Staging: reduce concurrent builds from 3 to 2#51

Merged
krusche merged 1 commit intomainfrom
fix/staging-concurrent-builds
Feb 1, 2026
Merged

Staging: reduce concurrent builds from 3 to 2#51
krusche merged 1 commit intomainfrom
fix/staging-concurrent-builds

Conversation

@krusche
Copy link
Member

@krusche krusche commented Feb 1, 2026

Summary

  • Reduced concurrent build size from 3 to 2 for all staging build agents

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:

  • Build timeouts
  • Stale build jobs that had to be force-cancelled
  • Failed builds

Changes

  • artemis_staging1.yml: concurrent_build_size 3 → 2
  • artemis_staging2.yml: concurrent_build_size 3 → 2
  • artemis_staging_localci_nodes_buildagent.yml: concurrent_build_size 3 → 2

Testing

Already applied manually to staging1 build agents and verified working via the REST API:

staging1agent01: maxConcurrent=2
staging1agent02: maxConcurrent=2
staging1agent03: maxConcurrent=2

Summary by CodeRabbit

  • Chores
    • Reduced concurrent build capacity in staging environments from 3 to 2, which may impact build queue throughput and processing times.

✏️ Tip: You can customize this high-level summary in your review settings.

@krusche krusche requested a review from a team as a code owner February 1, 2026 14:12
@coderabbitai
Copy link

coderabbitai bot commented Feb 1, 2026

Warning

Rate limit exceeded

@krusche has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 11 minutes and 28 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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.

📝 Walkthrough

Walkthrough

Three staging environment configuration files have been updated to reduce the concurrent_build_size parameter from 3 to 2 under their local CI settings, decreasing the number of allowed parallel builds.

Changes

Cohort / File(s) Summary
Local CI Configuration Updates
group_vars/artemis_staging1.yml, group_vars/artemis_staging2.yml, group_vars/artemis_staging_localci_nodes_buildagent.yml
Decreased concurrent_build_size from 3 to 2 under continuous_integration.localci across three staging environment configurations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Three builds once danced with vigor and pace,
But two's the tempo that wins the race!
From staging to staging, the reduction flows,
A leaner pipeline—configuration glows! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Staging: reduce concurrent builds from 3 to 2' directly and accurately summarizes the main change across all three modified staging configuration files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix/staging-concurrent-builds

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.

❤️ Share

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

@krusche krusche force-pushed the fix/staging-concurrent-builds branch from c323f40 to 1ff7dd6 Compare February 1, 2026 14:24
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.
@krusche krusche force-pushed the fix/staging-concurrent-builds branch from 1ff7dd6 to 48adc95 Compare February 1, 2026 14:25
@krusche krusche merged commit e5cc292 into main Feb 1, 2026
1 check passed
@krusche krusche deleted the fix/staging-concurrent-builds branch February 1, 2026 14:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant