Bamboo Remote Agent JVM alignment during server version upgrades

Upgrading a Bamboo server often introduces a new required Java runtime version. While the server is updated, existing remote agents may continue to run on an older JVM, creating a compatibility boundary between the server's communication protocol and the agent's runtime environment.

The primary goal is to maintain agent connectivity and ensure that build capabilities are accurately rediscovered across a distributed fleet without causing registration failures during the transition period.

Since agents discover JDK capabilities at startup, a mismatch between the server's expected version and the agent's current JAVA_HOME can lead to inconsistent job scheduling or total agent disconnection.

• What is the specific behavior of the agent-to-server protocol when a remote agent version lags behind the server's minimum supported JVM?
• Does Bamboo support a grace period for mixed-version agent fleets during a Data Center cluster upgrade?