We use a fairly standard build across most of our dev / testing servers, including our common tools (debuild, gcc, prove, etc). As far as I can tell, Bamboo requires me to configure each agent that comes online with each of the binaries that are installed that the various jobs will need.
As we grow I can see this maintenance task getting larger & larger, both as we add / replace remote agents and as we add more tasks to each of our plans.
Given that I've already provided a name & path to an executable once (e.g. gcc: /usr/bin/gcc), can Bamboo automatically pick this up on all future agents?
If all your agents are the same, you can create a single bamboo-capabilities.properties file that lists all your common capabilities and provide it to the agent at startup.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@James Dumay [Atlassian] Yeah. Well its not working^^
echo $PATH
cat /root/bamboo-agent-home/bin/bamboo-capabilities.properties
system.builder.command.Docker-Compose /usr/local/bin/docker-compose
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The docs don't say how to define custom executables, and I've tried a few things (like system.scons=/usr/bin/scons or system.scons.executable=/usr/bin/scons) but can't make it "go" (they all just end up in Custom). Any hints please?
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.