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,364,116
Community Members
 
Community Events
168
Community Groups

Is it possible to specify an environment for a custom command using a capability

We provide lots of tools on our agents, but some of those tools require specific environment variables to be set.

e.g.

we have multiple node versions installed. Each of those node versions provide access to some tools like bower.

To expose bower we specify a capability like this:

system.builder.command.bower-8.9.4=/home/bamboouser/.nvm/versions/node/v8.9.4/bin/bower

But in order to make it work for the user i would have to expose a specific PATH like

PATH=/home/bamboouser/.nvm/versions/node/v8.9.4/bin:.....

 

is it possible to preconfigure such an environment for a given custom command capability?

 

Thanks in advance,

  Korbinian

1 answer

Hi Korbinian, all bamboo variables are exported to the session on the agent. For example the variable system.builder.command.bower-8.9.4 are accesible for you on the agent like this system_builder_command_bower-8.9.4 you can modify you script and setup the path using environment exported.

A technique that a I haved was print env (linux) or get-childitem env: (windows) on a task for inspect variables tha bamboo injects on the agent on each session.

Cheers.  

i know that that it is possible that way. The problem i try to solve is that people currently need to know that they have to setup the environment in such a way.

 

it would be very cool if our developers could just:

  • select the command task
  • select the executable
  • setup the arguments for the command
  • and be all setup

without having to set e.g. PATH=... or NVM_HOME=... or whatever is required.

 

Cheerio,

  Korbinian

+1 for the cool idea!

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events