jbe vs. server version compatibility
With RTC 3.0 on the horizon, we've started wondering about managing
the the transition in our production build environment. With many build
machines running multiple JBE's and numerous RTC server instances,
we're trying to develop a "rolling upgrade strategy". One big concern is
JBE vs. server compatibility. Will a 3.0 server be able to drive builds
through 2.x JBE's? Alternatively, if we deploy 3.0 JBE's, will our existing
2.x servers be able to run builds against them? Or, will we have to
upgrade to 3.0 JBE's at the same time we upgrade the RTC server side?
the the transition in our production build environment. With many build
machines running multiple JBE's and numerous RTC server instances,
we're trying to develop a "rolling upgrade strategy". One big concern is
JBE vs. server compatibility. Will a 3.0 server be able to drive builds
through 2.x JBE's? Alternatively, if we deploy 3.0 JBE's, will our existing
2.x servers be able to run builds against them? Or, will we have to
upgrade to 3.0 JBE's at the same time we upgrade the RTC server side?
Accepted answer
One other answer
For 3.0, the 2.x clients are not compatible with 3.0. This includes JBE. So you will need to upgrade the JBEs at the same time as the server.
We had wanted to provide improved compatibility between back-level clients and a new server (across the board, not just for JBE), to allow exactly this kind of staged upgrade, but unfortunately that work got deferred due to other priorities.
We had wanted to provide improved compatibility between back-level clients and a new server (across the board, not just for JBE), to allow exactly this kind of staged upgrade, but unfortunately that work got deferred due to other priorities.