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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


Single checkout code and run multiple jobs in parallel



I would like to run multiple jobs in parallel on the same automation server.  In order to do this, do I need to install an additional local agent or an additional remote agent?

When I try to install an additional remote agent the installer picks the location of the first agent that is already installed on the automation server. 

What I did was: I turned off the first agent and then run the installer for the new remote agent.

What is the correct process to install an addition agent (I do not see the option 'add local agent') So I am guessing that I need to install an additional 'remote agent'.




1 answer

1 accepted

1 vote
Answer accepted
Eduardo Alvarenga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Feb 14, 2023

Hello @Archie Sangole,

Welcome to Atlassian Community!

Choosing between a Local or Remote Agent requires some understanding of the overall Bamboo architecture. Local Agents will share the same resources (memory/CPU/disk/etc) with the Bamboo Server instance, meaning that any agent instructions that are launched by that Local Agent will compete with the main Bamboo application for those resources. Local Agents are deprecated and will be removed in a future Bamboo release.

Remote Agents are independent, they will not compete with the same resources used by the Bamboo JVM. Though they can still compete for memory, CPU and disk if they are installed on the same server that runs the Bamboo instance, likely they will reserve memory for their own JVMs and will at least not break each other in terms of memory.

To install multiple Bamboo Remote Agents on the same server, you need to specify a "-Dbamboo.home" property to the installer to indicate the Agent's home folder:

java -Dbamboo.home=/home/bamboo/bamboo-agent-2 -jar atlassian-bamboo-agent-installer-X.X.jar ...

For more information, please read the Bamboo Remote Agent installation guide and also check the Additional remote agent options page for more installation options


Eduardo Alvarenga
Atlassian Support APAC

--please don't forget to Accept the answer if the reply is helpful-- 

Hi Eduardo, 

Thank you for the quick response. With the above information I was able to install a second remote agent. I configured it as a service, the same way as I did the first one. 

Modified the service file permissions chmod 644 

Running the following cmd gives:

systemctl installstart bamboo-agent-2.service

However the service fails to start. Perhaps I am missing a step. 

Below is the output of the systemctl cmd: 


systemctl status bamboo-agent-2.service

  • bamboo-agent-2.service - Atlassian Bamboo startup Agent

     Loaded: loaded (/etc/systemd/system/bamboo-agent-2.service; enabled; vendor preset: enabled)

     Active: failed (Result: exit-code) since Wed 2023-02-15 10:56:35 EST; 6min ago

    Process: 5503 ExecStart=/home/trcauto/bamboo-agent-home-2/bin/ start & (code=exited, status=1/FAILURE)

        CPU: 113ms




Hi Eduardo, 

Please ignore the my previous comment. After running the following cmd: 

systemctl enable bamboo-agent-2

 and restarting the automation server, the service is now running. 

Thank you for your help. 



Like Steffen Opel _Utoolity_ likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events