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

This widget could not be displayed.

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

https://confluence.atlassian.com/display/BAMBOO/Bamboo+Best+Practice+-+Using+Agents#BambooBestPractice-UsingAgents-Unknowncapabilities 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 -- https://marketplace.atlassian.com/plugins/com.alienfast.bamboozled.ruby.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?

This widget could not be displayed.

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

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

This widget could not be displayed.

If you your machine installations are similar, you can define own bamboo-capabilities.properties see https://confluence.atlassian.com/bamboo/configuring-remote-agent-capabilities-using-bamboo-capabilities-properties-289276849.html

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

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Wednesday in New to Jira

Are you planning to trial, or are currently trialling Jira Software? - We want to talk to you!

Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in   talking to 20 people planning t...

125 views 2 0
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you