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

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?

1 answer

1 accepted

1 vote
Accepted answer

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

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

4,341 views 20 13
View question

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you