Using High Availability (active/active) in your controllers has several implications about how your builds behave, how they are scheduled across your controller replicas and some build-related plugins work. This page contains a collection of important considerations about this topic. |
Running builds
CloudBees has tested a range of builds and triggers in High Availability (active/active) mode to clarify use cases for CloudBees CI High Availability. Pipeline projects are the focus of using HA (High Availability) mode, and are thus expected to work without limitations. Some exceptions are documented below.
Build scheduling and explicit load balancing
Starting with version 2.426.1.2, CloudBees CI provides explicit load balancing for controllers running in HA (High Availability) mode.
Explicit load balancing redirects new builds to the the controller replica with the least load.
CloudBees CI calculates the load using a simple metric that considers the following factors:
|
CloudBees CI provides explicit load balancing in most cases. The table below summarizes supported and unsupported cases:
Job type | Scheduling strategy |
---|---|
Interactive trigger (Build Now) |
Replica with the least work load |
Scheduled build (Cron job) |
Replica with the least work load |
Branch Indexing (Multibranch and Organization folder jobs) |
Replica with the least work load |
Webhooks (including multibranch events) |
Replica with the least work load |
REST API Triggers |
Replica with the least work load |
Replica with the least work load |
|
Always the same replica as the upstream build |
|
Replica with the least work load |
|
Any other trigger type |
Same replica that processed the trigger |