Is it possible to use different grails executables across branches in a single plan

[Will Dampney]

I have a Grails plugin in a git repository that current has two development branches built against different grails versions:

* master - grails 2.4.3

* branch - grails 2.3.7

Bamboo is able to access both branches, but the stages of the build seemingly have to relate to a single executable across the branches (e.g. grails 2.4.3).

Is it possible, by means of variables or otherwise, to have the master running the grails 2.4.3 executable and the branch running grails 2.3.7?

[Krystian Brazulewicz · Accepted solution]

Unfortunately the answer is no. ATM there's no way to do it other than using the script task and branch variables to point to the correct grails binary.

We had this problem internally as well when we migrated our toolset. To address this problem we:

• cloned our plan and reconfigured a clone to use new toolset
• renamed the original plan to "Legacy ...."
• disabled automatic branch detection for old plan

[Will Dampney]

Thanks Krystian, thats basically the workaround we've had to implement. If we move Bamboo to a Linux environment in the future, we might be able to use gvm (groovy environment manager) to make a better scripted solution.