Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,465,032
Community Members
 
Community Events
176
Community Groups

Can a bamboo agent get started already dedicated?

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!

1 answer

1 accepted

0 votes
Answer accepted

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

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events