Can a bamboo agent get started already dedicated?

[Jonathan Ghellere]

Hello Community!

Can we start a new fresh agent already dedicated to a plan/job/project?

Sometimes we hit a limit between the number of JOBs vs. Agents. We want to bring up an agent already dedicated to a Plan or a specific Job, because this one plan or job need to be processed first. There's any config on the agent side that forces the agent to register to Bamboo server already dedicated?

I know I could change my jobs to be "requirements" driven, but ignore that please.

ps. I wonder if there's something related to this via wrapper.conf, like we have the "disable capabilities auto detection".

Thx!

[Eduardo Alvarenga · Accepted solution]

Hello @Jonathan Ghellere

The Agent dedication is controlled by the Bamboo Server and cannot be defined at the Agent level. No settings are available on the agent that would control how it is dedicated on startup.

Dedicating an Agent is not an Agent setting, but a Project/Plan/Job setting, so the Agents are not modified at all.

We have an FR https://jira.atlassian.com/browse/BAM-8741 that was closed due to low engagement which suggests that Agents could start in a disabled state. 

As a workaround, you can "Pause" the server queue, add the Agent, set the dedication and "Unpause" the server. That will guarantee that no Builds will be triggered on the agent during the pause duration.

To Pause/Unpause the server:

curl -k -u admin:admin -H 'Accept: application/json' -X POST <bamboo_url>/rest/api/latest/server/pause?os_authType=basic

curl -k -u admin:admin -H 'Accept: application/json' -X POST <bamboo_url>/rest/api/latest/server/resume?os_authType=basic

You can also POST the Pause/Unpause commands through the UI:

• Bamboo Administration -> Manage Apps -> Pause/Unpause

Regards,

Eduardo Alvarenga
Atlassian Support APAC