Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do I autodetect capabilities on a Bamboo Remote Slave?

In the Capabilities section, it is very easy to get the Bamboo server to auto-detect capabilities, but in a massive build environment, where you have dozens of slaves - how do you get them to auto-detect their own capabilities?

3 answers

0 votes
rsperafico Atlassian Team Feb 12, 2015

Hello Richard,

Thank you for your question.

There are some capabilities will be picked up when you start the remote agent (by looking at the environment variables you have set up in the remote agent box, i.e.: M2_HOME) and others that you have to add manually.

If you find this answer useful, I would kindly ask you to accept it so the same will be visible to others who might be facing the same issue you have inquired.

Thank you for your understanding.

Kind regards,
Rafael P. Sperafico
Atlassian Support That doc says that it should be possible to trigger a detection via: Bamboo admin > Agents > ${AGENT} > Detect Server Capabilities But that doesn't seem to be the case. The Bamboozled Ruby Plugin -- -- requires auto detection in order to find the ruby runtime capability. Is it a bug that the "Detect Server Capabilities" option is no longer available?

Can you provide a list of which environment variables the remote agent uses, and any other places it searches?

For example, the main Bamboo server has auto-detected Oracle JDK installed at /usr/java/latest (which points to /usr/java/jdk1.7.0_65); however, when I added

export JAVA_HOME=/usr/java/latest

to ~bamboo/.bashrc on the remote host and restarted the Bamboo Agent, the capabilities screen does not report this.


UPDATE:  Additionally, in the bamboo agent log, I see this:


[Jdk] Environment variable JAVA_HOME does not point to valid JDK
rsperafico Atlassian Team Feb 12, 2015

Hello Richard, Thank you for your update. What happens when you run "which java" from terminal? Does the same outputs "/usr/java/latest/bin/java" ? Have you updated .bashrc by reloading it after changes being made? (ie.: source ~bamboo/.bashrc) — Kind regards, Rafael P. Sperafico Atlassian Support

Yes, I have done all of the above. When I run which java, it resolves as /usr/java/latest/bin/java

If you your machine installations are similar, you can define own see

You can also make own script autodetecting SW and creating the if your installations differ.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bamboo

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

195 views 4 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you