We are using Bamboo 6.3.1 with 10 remote agents to run our builds. The stock image we use is ami-a450d4dd.
We are currently building with C3 agents which has their own local SSD storage. This works fine.
I've tried to use the C5 agents instead, but the build jobs run out of disk space on the agents, and I can't find anywhere how to make them any larger. I need more space in the build-folder of the agent. I realize I can attach another EBS volume to the agent, but I would like everything to clean up nicely, like the agent build folder.
If I try to launch ami-a450d4dd directly from AWS i'm presented with a choice of how much storage size to put on the root volume, I would guess Bamboo somewhere gives AWS that information when it is creating the volume for the instance. I would like to make it larger than the 10 GB which seems to be default.
Hi Christian,
You might be aware of this already, but given that Managing your elastic image configurations and related pages do not yet document this at all, and neither do the resp. release notes, I'll mention that this feature is available as of Bamboo 6.6.0, here's a screenshot:
Hi Christian,
We have a document explaining how to do that:
If any question remains after reading the documentation, let us know.
Thank you.
best,
Gabriel Ribeiro
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Gabriel Ribeiro Thanks for your answer. Although after reading the information that you provided, it seems suggestions that we should attach a new EBS to the instance. What @Christian Strøyer was asking (and I also would like to do) is to change the default root volume size attached to the agent when it starts, and not attach a new volume to it.
Do we have this setting in Bamboo?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I eventually managed to get our build running with EBS on C4 instances. I was surprised with the complexity of this task, since I was expecting a simple way to expand the disc space, which must basically just be a value passed to the elastic instance.
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.