RELEASED: Public: September 4, 2024
New features
- Better HTTP response code when maximum load per replica exceeded (BEE-49664)
-
When the “Maximum load per replica” setting is configured on a High Availability (HA) controller, and the actual load reached the configured maximum, HTTP requests to trigger builds produced 302 responses. This was consistent with the behavior of Jenkins when refusing to schedule builds, or when a build was already scheduled and the trigger would duplicate it, but misleading in this context. A 429 Too Many Requests response is now served, along with Retry-After, X-Current-Load, and X-Maximum-Load headers (the load counts are for the controller as a whole, not a single replica).