I am struggling a little bit to get Gradle running with Elastic Bamboo. I would install Gradle on our mounted EBS-Snapshot. Then take a new one and afterwards add this as Executable capability to the elastic image config. Is this enough? Since normally (like this guide: http://exponential.io/blog/2015/03/30/install-gradle-on-ubuntu-linux/) you would also manipulate your profile - but this is located on the ephemeral EBS of the image...
Use this script (e.g. for Gradle 2.5):
mkdir -p ~/mnt/bamboo-ebs/gradle && cd $_
wget https://services.gradle.org/distributions/gradle-2.5-bin.zip
unzip gradle-2.5-bin.zip
Then take a new snapshot from the EBS volume and use this in your elastic agent.
Afterwards add "Executable Capability" to your image configuration with this as path:
*/mnt/bamboo-ebs/gradle/bin/gradle*
Now you can use Gradle as Command in Build plans and add the task name as argument - e.g. "build".
I don't use gradle, but similarly I've had to install tools I need and make them available to all build nodes. If you've installed it on a node's EBS volume and have verified it works, then you're most of the way there. You just need to create a snapshot and associate with your image.
Here's the docs on how to do it:
https://confluence.atlassian.com/display/BAMBOO/Configuring+elastic+instances+to+use+the+EBS
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.