Bamboo remote agent installation guide

This page describes how to install the Bamboo Remote Agent manually.

Before you begin:

Note that you can run multiple Bamboo agents on the same machine – you just need to provide a separate home directory for each agent installation.

Step 1. Enable remote agent support

  1. Click the  icon in the Bamboo header and choose Overview.
  2. Click Agents (under 'Build Resources')
  3. Click either Enable Remote Agent Support or Disable Remote Agent Support.

Read more about enabling and disabling remote agent support here.

Step 2. Download and install the remote agent

  1. Create a directory on the agent machine (e.g. bamboo-agent-home) to serve as the Bamboo agent home for the remote agent.
  2. Click the  icon in the Bamboo header and choose Overview.
  3. Click Agents in the left panel (Under Build Resources). This will display the 'Agents' screen, showing lists of all local agents and all remote agents that currently exist on your Bamboo system.
  4. If not already enabled, click the Enable remote agent support link 
  5. Click Install Remote Agent. The 'Installing a remote agent' screen will display
  6. Click DOWNLOAD Remote Agent JAR and save the JAR file to the directory on the agent machine that you created above.
  7. Copy the command under 'Running a Remote Agent' to the clipboard for use in Step 3 that follows.

Step 3. Launch the remote agent

Once installed, run the remote agent by executing the command line obtained above. This command will look something like this:

Where X.X represents your Bamboo version number.

(info) The name of the jar file, for example, atlassian-bamboo-agent-installer-5.4-SNAPSHOT.jar, will vary depending on the version of Bamboo you are running.

You can run the remote agent with a number of additional command line parameters. Configuration options include remote agent data storage, capability detection and logging, suppression of self-signed certificate and running without the Remote Agent Supervisor or with different start-up commands.

See Additional remote agent options for more information.

If you are having issues launching the agent, then take a look at our troubleshooting guide.

Step 4. Configure the remote agent's capabilities

All remote agents feature a capability that can be defined. Examples include an executable, such as Maven, a JDK, a DVCS client or a custom capability. They typically define the path to an executable that has already been installed, and must be defined in Bamboo before Bamboo or its agents can make use of them.

Capabilities can be defined specifically for an agent, or shared between all local or all remote agents.

Please see Configuring capabilities for more on defining capabilities.

Was this helpful?

Thanks for your feedback!

47 Archived comments

  1. User avatar

    Matt Doar (ServiceRocket)

    I want to run a remote agent at startup of a machine, and I see a suggestion to consult OS docs for that. It would be more helpful to provide examples for Linux and Windows as JIRA and Confluence do.

    25 Jul 2008
  2. User avatar

    Boris Capitanu

    Mac OSX 10.4+ users:

    If you want to set up the Bamboo agent to automatically start up on a OSX system, create a file called com.atlassian.BambooAgent.plist in folder /Library/LaunchDaemons/ whose content is: (you need to edit the file to replace YOUR_BAMBOO_AGENT_HOME, YOUR_BAMBOO_SERVER, YOUR_LOG_FOLDER, USERNAME_TO_RUN_WITH with proper values for your installation)

    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
            <key>Disabled</key>
            <false/>
            <key>Label</key>
            <string>com.atlassian.BambooAgent</string>
            <key>OnDemand</key>
            <false/>
            <key>ProgramArguments</key>
            <array>
                    <string>/usr/bin/java</string>
                    <string>-Xmx1024m</string>
                    <string>-Dbamboo.home=YOUR_BAMBOO_AGENT_HOME</string>
                    <string>-jar</string>
                    <string>/usr/local/BambooBuildAgent/bamboo-agent-2.1.5.jar</string>
                    <string>http://YOUR_BAMBOO_SERVER/agentServer/</string>
            </array>
            <key>RunAtLoad</key>
            <true/>
            <key>ServiceDescription</key>
            <string>Atlassian Bamboo build agent</string>
            <key>StandardErrorPath</key>
            <string>YOUR_LOG_FOLDER/bamboo-agent-launchd.err</string>
            <key>StandardOutPath</key>
            <string>YOUR_LOG_FOLDER/bamboo-agent-launchd.out</string>
            <key>UserName</key>
            <string>USERNAME_TO_RUN_WITH</string>
    </dict>
    </plist>
    

    Enjoy.

    26 Jan 2009
    1. User avatar

      Anonymous

      Hi,

      Is it possible to start the Bamboo server on OS X automatically a similar manner as you have described, I have done a brief search around atlassian but have not found anything so far.  

      Thanks!

      02 Mar 2009
    1. User avatar

      Bernard Davison

      With Lion (MacOS X 10.7) I've found that the above plist didn't work with version 3.3.2. but it set me on the right track. The following works a treat however.

      <?xml version="1.0" encoding="UTF-8"?>
      <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
      <plist version="1.0">
      <dict>
      <key>Disabled</key>
      <false/>
      <key>Label</key>
      <string>com.atlassian.BambooAgent</string>
      <key>OnDemand</key>
      <false/>
      <key>ProgramArguments</key>
      <array>
      <string></full/path/to/bamboo-home>/bin/bamboo-agent.sh</string>
      <string>console</string>
      </array>
      <key>RunAtLoad</key>
      <true/>
      <key>ServiceDescription</key>
      <string>Atlassian Bamboo build agent</string>
      <key>StandardErrorPath</key>
      <string></full/path/to/bamboo-home>/logs/bamboo-agent-launchd.err</string>
      <key>StandardOutPath</key>
      <string></full/path/to/bamboo-home>/logs/bamboo-agent-launchd.out</string>
      </dict>
      </plist>
      You may also want to add
      <key>UserName</key>
      <string>USERNAME_TO_RUN_WITH</string>
      Also have a read of http://en.wikipedia.org/wiki/Launchd

      This also works for the Bamboo server.

      21 Nov 2011
  3. User avatar

    Bob Swift [Bob Swift Atlassian Add-ons]

    Suggest you add to the documentation the ability for windows users to customize ...\conf\wrapper.conf file and that the ...\bin\InstallBambooAgent-NT.bat can be used after the customization. Running the remote agent jar will always replace the file, so this is the only way to customize it. For instance, you can run the remote agent jar command first so that the wrapper config gets created, remove the service, customize wrapper.conf, and then re-install the service with the wrapper command. For instance, this can customize the Windows service name.

    11 Oct 2009
  4. User avatar

    Matthew Hinkle

    Hello all,

    I used this page to help me download, install, and launch the new remote agent successfully but after 10-20 minutes the agent becomes unresponsive and goes offline.

    Does anyone know why this would happen and how I can prevent this?

    We had the same remote agent set up on a different server and it never went offline...

    Although, the log does show that the old agent did get "marked as inactive". but a "new one came in place" so it never went offline... 

    marked as inactive. A new one came in place.

    Jun 21, 2010 10:12:26 AM Remote agent "servername.domainname" came back after a period of inactivity.

    Thanks for any help!

    08 Jul 2010
    1. User avatar

      Giles Gaskell

      Hello Matthew,

      My apologies for the delay in response. If this issue has not been addressed, then to get a speedier response, I would recommend either lodging a support ticket or posting a forum message via the links at the end of this page (below).

      Kind regards,
      Giles.

      09 Aug 2010
  5. User avatar

    Anonymous

    Hello, I 'm trying to run the remote agent as a service on a windows XP sp2 32 bits but still fails.

    I installed it with

    java -jar atlassian-bamboo-agent-installer-2.2.1.jar http://10.30.230.28:8085/agentServer/ installntservice

    then I tried to run it with both the service.msc window and the command net start "Bamboo Remote Agent".

    Both fails with

    The Bamboo Remote Agent service is starting.....
    The Bamboo Remote Agent service could not be started.
    A system error has occurred.
    System error 1067 has occurred.
    The process terminated unexpectedly.

    I also tried java -jar atlassian-bamboo-agent-installer-2.2.1.jar http://10.30.230.28:8085/agentServer/ start but then I got

    STATUS | wrapper  | 2010/09/15 17:43:42 | Starting the Bamboo Remote Agent service...
    INFO   | wrapper  | 2010/09/15 17:43:47 | Waiting to start...
    ...
    INFO   | wrapper  | 2010/09/15 17:45:04 | Waiting to start...
    ERROR  | wrapper  | 2010/09/15 17:45:09 | The Bamboo Remote Agent service was launched, but failed to start.
    Wrapper terminated with non zero exit code: 1
    Destroying underlying agent process...

    15 Sep 2010
    1. User avatar

      Anonymous

      I've just came across the same problem...Is anybody know how to solve it?

      Windows XP is my non-bamboo-server PC.

      28 Jun 2011
      1. User avatar

        Anonymous

        You should change the startup profile for the service. By default it runs from the SYSTEM and can not create necessary directories. Change the service startup profile to any existing admin account on the machine.

        04 Apr 2012
        1. User avatar

          Mujahed

          I have installed Bamboo agent on windows 2008 server, and its going offline every time even if we run the services through the administrator. 

          INFO   | jvm 7    | 2014/01/21 19:07:44 |     at org.tanukisoftware.wrapper.WrapperSimpleApp.run(WrapperSimpleApp.java:240)
          INFO   | jvm 7    | 2014/01/21 19:07:44 |     at java.lang.Thread.run(Thread.java:744)
          INFO   | jvm 7    | 2014/01/21 19:07:44 | Caused by: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
          INFO   | jvm 7    | 2014/01/21 19:07:44 |     at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:385)
          INFO   | jvm 7    | 2014/01/21 19:07:44 |     at sun.security.validator.PKIXValidator.engineValidate(PKIXValidator.java:292)
          INFO   | jvm 7    | 2014/01/21 19:07:44 |     at sun.security.validator.Validator.validate(Validator.java:260)
          INFO   | jvm 7    | 2014/01/21 19:07:44 |     at sun.security.ssl.X509TrustManagerImpl.validate(X509TrustManagerImpl.java:326)
          INFO   | jvm 7    | 2014/01/21 19:07:44 |     at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:231)
          INFO   | jvm 7    | 2014/01/21 19:07:44 |     at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:126)
          INFO   | jvm 7    | 2014/01/21 19:07:44 |     at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1323)
          INFO   | jvm 7    | 2014/01/21 19:07:44 |     ... 28 more
          INFO   | jvm 7    | 2014/01/21 19:07:44 | Caused by: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
          INFO   | jvm 7    | 2014/01/21 19:07:44 |     at sun.security.provider.certpath.SunCertPathBuilder.engineBuild(SunCertPathBuilder.java:196)
          INFO   | jvm 7    | 2014/01/21 19:07:44 |     at java.security.cert.CertPathBuilder.build(CertPathBuilder.java:268)
          INFO   | jvm 7    | 2014/01/21 19:07:44 |     at sun.security.validator.PKIXValidator.doBuild(PKIXValidator.java:380)
          INFO   | jvm 7    | 2014/01/21 19:07:44 |     ... 34 more
          ERROR  | wrapper  | 2014/01/21 19:07:44 | JVM exited while starting the application.
          FATAL  | wrapper  | 2014/01/21 19:07:44 | There were 5 failed launches in a row, each lasting less than 3 seconds.  Giving up.
          FATAL  | wrapper  | 2014/01/21 19:07:44 |   There may be a configuration problem: please check the logs.
          STATUS | wrapper  | 2014/01/21 19:07:44 | <-- Wrapper Stopped

          21 Jan 2014
  6. User avatar

    Anonymous

    Is a Bamboo remote agent what I need to run a Bamboo build on a PC other than the Bamboo server PC?

    09 Dec 2010
    1. User avatar

      Anonymous

      yes

      14 Dec 2010
  7. User avatar

    Chris Ferry

    Hey,

    Why don't you provide an /etc/init.d bamboo remote agent script?  Would be a nice thing to do don't you think?

    In fact even better, provide apt and rpm packages.

    That would be the right thing to do.

    13 Sep 2011
    1. User avatar

      Anonymous

      Seconded.  

      17 Dec 2011
      1. User avatar

        Bill Cernansky

        Thirded

        26 Mar 2013
        1. User avatar

          Anonymous

          Couldn't agree more

          26 Apr 2013
          1. User avatar

            vince maraia

            fourth - 100 times agree

            23 Jul 2014
            1. User avatar

              Sewa Makhinya

              Runing bamboo remote agents thru init.d-scripts described here: http://wiki.paparazziuav.org/wiki/Builds/Bamboo-agents

              31 Jul 2014
  8. User avatar

    Anonymous

    Could not get it started - it fails due to java.lang.NumberFormatException

     

    INFO   | jvm 1    | 2012/06/22 01:35:29 | ---- Debugging information ----

    INFO   | jvm 1    | 2012/06/22 01:35:29 | message             : For input string: "2012-06-22 08:29:48.186 UTC"

    INFO   | jvm 1    | 2012/06/22 01:35:29 | cause-exception     : java.lang.NumberFormatException

    INFO   | jvm 1    | 2012/06/22 01:35:29 | cause-message       : For input string: "2012-06-22 08:29:48.186 UTC"

    INFO   | jvm 1    | 2012/06/22 01:35:29 | class               : java.util.Date

    INFO   | jvm 1    | 2012/06/22 01:35:29 | required-type       : java.util.Date

    INFO   | jvm 1    | 2012/06/22 01:35:29 | converter-type      : com.thoughtworks.xstream.converters.SingleValueConverterWrapper

    INFO   | jvm 1    | 2012/06/22 01:35:29 | wrapped-converter   : com.atlassian.bamboo.persister.xstream.SecondsDateConverter

    INFO   | jvm 1    | 2012/06/22 01:35:29 | path                : /result/value/creationDate

    INFO   | jvm 1    | 2012/06/22 01:35:29 | line number         : 4

    INFO   | jvm 1    | 2012/06/22 01:35:29 | class[1]            : com.atlassian.bamboo.v2.build.agent.RemoteAgentDefinitionImpl

    INFO   | jvm 1    | 2012/06/22 01:35:29 | converter-type[1]   : com.thoughtworks.xstream.converters.reflection.ReflectionConverter

    INFO   | jvm 1    | 2012/06/22 01:35:29 | class[2]            : org.springframework.remoting.support.RemoteInvocationResult

    INFO   | jvm 1    | 2012/06/22 01:35:29 | version             : null

    22 Jun 2012
  9. User avatar

    Anonymous

    Is there any way to preconfigure build-dir? (Windows)

    02 Jul 2012
  10. User avatar

    Kyle O'Connor

    If I set custom JVM sizings in the wrapper.conf, does this apply to just the agent process itself, or to the builds that will run on it?

    08 Aug 2012
  11. User avatar

    Gili

    To auto-start under Ubuntu, do the following:

    1. Install Remote Agent as usual (the following assumes you installed under user "bamboo").
    2. Once the agent is registered, stop the process (CTRL+C).
    3. "sudo nano /etc/init/bamboo-agent.conf"
    4. Paste the following contents into the file:

    That's it. The remote agent will now start up on boot.

     

    These instructions are based on: http://ubuntuforums.org/showthread.php?t=1689525

    16 Sep 2012
  12. User avatar

    Anonymous

    I'm currently trying to evaluate the tool but i'm stuck with this error. The remote client can't start.  

     

    [WrapperSimpleAppMain] [AgentContext] Bootstrap Type: 'REMOTE'
    INFO | jvm 1 | 2012/10/19 14:43:16 | 2012-10-19 14:43:16,612 INFO [Thread-1] [RemoteAgent] com.atlassian.bamboo.v2.build.agent.remote.RemoteAgent starting.
    INFO | jvm 1 | 2012/10/19 14:43:16 | 2012-10-19 14:43:16,722 INFO [Thread-1] [RemoteAgentHomeLocatorForBootstrap] Agent home located at 'C:\Documents and Settings\svnbuild\bamboo-agent-home'
    INFO | jvm 1 | 2012/10/19 14:43:16 | 2012-10-19 14:43:16,737 INFO [Thread-1] [RemoteAgent] Starting Bamboo Remote Agent...
    INFO | jvm 1 | 2012/10/19 14:43:16 | 2012-10-19 14:43:16,737 INFO [Thread-1] [RemoteAgent] Starting application context...
    INFO | jvm 1 | 2012/10/19 14:43:17 | 2012-10-19 14:43:17,753 WARN [Thread-1] [PropertyPlaceholderConfigurer] Could not load properties from class path resource [bamboo-init.properties]: class path resource [bamboo-init.properties] cannot be opened because it does not exist
    INFO | jvm 1 | 2012/10/19 14:43:17 | 2012-10-19 14:43:17,784 INFO [Thread-1] [RemoteAgentHomeLocatorForBootstrap] Agent home located at 'C:\Documents and Settings\svnbuild\bamboo-agent-home'
    INFO | jvm 1 | 2012/10/19 14:43:17 | 2012-10-19 14:43:17,784 INFO [Thread-1] [RemoteAgentHomeDirectoryLayout] Plugin directory: C:\Documents and Settings\svnbuild\bamboo-agent-home\plugins
    INFO | jvm 1 | 2012/10/19 14:43:17 | 2012-10-19 14:43:17,784 INFO [Thread-1] [RemoteAgentHomeDirectoryLayout] Plugin cache directory: C:\Documents and Settings\svnbuild\bamboo-agent-home\caches\plugins
    INFO | jvm 1 | 2012/10/19 14:43:17 | 2012-10-19 14:43:17,816 WARN [Thread-1] [AgentConfiguration] Configuration file does not exist. Creating File: bamboo-agent.cfg.xml
    INFO | jvm 1 | 2012/10/19 14:43:17 | 2012-10-19 14:43:17,831 INFO [Thread-1] [AgentUuidInitializer] Found agent UUID '1e9eca0a-6c06-4ba6-9009-691640ec2447' in temporary UUID file 'C:\Documents and Settings\svnbuild\bamboo-agent-home\uuid-temp.properties'
    INFO | jvm 1 | 2012/10/19 14:43:17 | 2012-10-19 14:43:17,831 INFO [Thread-1] [AgentConfiguration] Setting UUID in main config file to '1e9eca0a-6c06-4ba6-9009-691640ec2447'
    INFO | jvm 1 | 2012/10/19 14:43:17 | 2012-10-19 14:43:17,862 INFO [Thread-1] [BambooActiveMQConnectionFactory] Setting broker URL to 'failover:(tcp://atc-bamboo1:54663?wireFormat.maxInactivityDuration=300000)?maxReconnectAttempts=10&initialReconnectDelay=15000'
    INFO | jvm 1 | 2012/10/19 14:43:17 | 2012-10-19 14:43:17,956 INFO [Thread-1] [BambooActiveMQConnectionFactory] Setting broker URL to 'failover:(tcp://atc-bamboo1:54663?wireFormat.maxInactivityDuration=300000)?maxReconnectAttempts=10&initialReconnectDelay=15000'

    19 Oct 2012
  13. User avatar

    Anonymous

    Same problem for me as with the previous comment. I cannot get the remote client working on Mac.

    21 Oct 2012
  14. User avatar

    Anonymous

    Is there a way to automatically rename the bamboo agent at installation?

    10 Jan 2013
  15. User avatar

    Anonymous

    I need instruction on how to configure autostart of bamboo agent on Centos x64

    11 Mar 2013
    1. User avatar

      Anonymous

      You need to create an init script for this.

      12 Jul 2013
  16. User avatar

    Anonymous

    Hi,

    I used the method describe above to install the bamboo agent on Mac OSX and start it as daemon. But I would like to set up a custom PATH for the bamboo agent so some of the tools installed get precedence over the default Mac OSX ones. I am wondering where is the best place to insert the custom PATH variable. In the plist file for the launch daemon or in the conf xml file in bamboo home? Any help is appreciated.

    Thanks in advance

    04 Jun 2013
  17. User avatar

    Anonymous

    Suppressing the self-signed certificate of the server

    You might want to change the URL in the example to https:// (wink)

    12 Jul 2013
  18. User avatar

    Roman Shamritskiy

    Mg12, I use Bamboo OnDemand and have the same problems. Did you manage to solve them?

    03 Dec 2013
    1. User avatar

      Przemek Bruski

      Remote agents are not supported on OnDemand. This feature request is tracked here: BAM-11870 - Support remote agents on Bamboo Cloud Open . Please comment and vote.

       

      03 Dec 2013
  19. User avatar

    Anonymous

    how to add bamboo-agent start-up service in mac os. If bamboo-agent is reboot, then it will automatically start on boot time.

     

    04 Dec 2013
    1. User avatar

      Armen Khachatryan [Atlassian]

      You can follow the recommendations from this page - Configuring Bamboo to start automatically on startup on Mac OS X

      04 Dec 2013
  20. User avatar

    Marian Zurek

    I would like to add the system variable(the env variable:SUCCESS_MESSAGE_LINES) to the remote agents. 

    Adding it to the server works as expected. However it does not propagate to the remote agent(s)

    What would be the best place to do so? conf/wrapper.conf in the agent's home dir?

    Configuring system properties does not mention it in details.

    Cheers, 

    Marian

     

     

    09 Sep 2014
  21. User avatar

    Brad Lynch

    Is it possible to run multiple remote agents on a single computer?

    10 Oct 2014
    1. User avatar

      Paul Watson [Atlassian]

      Yes, Brad, it is possible. You'll need to configure a separate home directory for each agent.

      12 Oct 2014
  22. User avatar

    Mark Bockstael

    We see quite some lagging happening. Even when manually starting a build when an agent is idle, it takes up to 5 minutes before it actually starts.
    The agent log shows :

    Any idea how this build queue check can be done more frequently?

     

    06 Nov 2014
  23. User avatar

    Michaelian

    Mark Bockstael: I have a similar problem but haven't had time to debug it.  Support suggested this document.  

    06 Nov 2014
  24. User avatar

    Ilya Panferov

    I have a problem with multiple Bamboo Agents
    We're currently running 4 remote agents on our deploy target to build & deploy our software.
    We've chosen 4 to avoid build queues, as we've usually have 4 concurent builds at once.

    The problem is, even though we've authorised each of them separately, babmoo shows only one agent in "Remote agents", and our builds are still blocking each other.
    Is there a point somewhere in remote agent setup that I have perhaps missed? 

    25 Nov 2014
  25. User avatar

    Walter Fore

    All,

     Ive been asked to create a remote bamboo agent - ok sounds simple enough - but the question is, do I have to have bamboo installed and running to create the remote agent via the console? I've looked for the java .jar file the doc refer to but the are no where to be found. I have watched a presentation on how to create a remote agent via the web, but, as you can probably guess, it was done through the console. That's really not a problem with me except I need a license. Any suggestions or recommendations? I can get a 90 license - which is not a problem either,, until 91 days have passed. 

    03 Feb 2015
  26. User avatar

    Sebastien Dubois

    For those interested, here's how I've configured my Bamboo Agent to run as a systemd service under RHEL 7.x. Note that my Bamboo agent and Bamboo server run on different hosts.

    • I've used the stand-alone agent jar (thus without the Java Service Wrapper)
      I've ensured that the Remote Agents were enabled on the Bamboo server and that the broker configuration was correct & reachable from my client machine

    • I've created a 'bamboo' user and a dedicated folder for the agent binaries & config under /var/bamboo-agent
    • I've created a dedicated keystore containing our Root CA, Intermediate CA & Server certificates (because I ran against the 'javax.net.ssl.SSLPeerUnverifiedException' exception). Note that my Bamboo server uses SSL & a certificate signed by our internal PKI

    • I've created a 'bamboo-capabilities.properties' file under /opt/bamboo-agent (reference: Configuring remote agent capabilities using bamboo-capabilities.properties)

    • I could then test the agent using the following

    • After that I've created a small bash script to start the agent

       

    • Script contents: 

       

    • I've then created a systemd service descriptor

       

    • Descriptor contents (note that in my case I require Docker to be up and running before the Bamboo agent):

       

    • Note that ideally, the ExecStart should directly start /bin/java ... -jar ... but I couldn't get it to work and consistently ran in the javax.net.ssl.SSLPeerUnverifiedException exception

    • After that I've registered the service and started it

    • To check the service logs

    • To stop/start the service

    Voilà! Hope this helps (smile) 

    18 Mar 2015
  27. User avatar

    Mahesh Vaidya

    Can I run more than one agents on a single machine.

    Use Case: I have 10 agents license but not as many servers at the moment ?

    04 Jun 2015
    1. User avatar

      Przemek Bruski

      Yes, you can run as many agents as your licence permits on a single host.

      05 Jun 2015
  28. User avatar

    Jason @ FPC

    This document is not clear enough about how Bamboo agents set the hostname / ip for the agent.

    Users need to configure a canonical hostname associated with the IP address the agent is listening on. A default hostname config in Linux is not sufficient and the result is that many Linux distros will tell the Bamboo Master the agent is localhost on 127.0.0.1 unless you add 1.2.3.4 canonical-hostname to /etc/hosts. Easy to do, but not obvious from the existing docs.

    16 Jun 2015
  29. User avatar

    Joshua Rosenkrans

    java -jar atlassian-bamboo-agent-installer-X.X-SNAPSHOT.jar http://bamboo-host-server:8085/bamboo/agentServer/ did not work for me. I had to omit the "/bamboo"

    Also, because I used the /bamboo the first time, I had to remove the /bamboo from the wrapper.conf file located in "/bamboo-agent/home/conf/" directory. I figured this out by reading the following stack overflow post: http://stackoverflow.com/questions/23817204/bamboo-remote-agent-http-404-on-fingerprint-request

    01 Jul 2015
    1. User avatar

      Jerry Qassar

      The example you are looking at assumes that you are aware of how you installed your Bamboo instance.

      If you use a context path, for example https://apps.mycompany.com/bamboo, then you must use /bamboo/agentServer for the agent.

      If you do not, for example https://bamboo.mycompany.com/, then you must use /agentServer.

      27 Jul 2015
Powered by Confluence and Scroll Viewport