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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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,552,475
Community Members
 
Community Events
184
Community Groups

Change capability_key during job

Hi,

we are using a bamboo-plugin, which needs a custom capability key with a specific installation path. But the installation is getting done during the job, so I have to reset the capability key to the new location of the installation. 

I googled and tried to find a solution, but could not find any. Maybe you guys have any ideas.

Cheers

 

1 answer

1 accepted

0 votes
Answer accepted
Daniel Santos
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 19, 2019

Hi @berkan_oeztuerk,

If I understood you correctly, you are trying to configure a capability that will be installed during a build and you don't know the path of it before its installation. Can you confirm that?

If this is the case, the only solution I can think of right now is:

  1. Set the custom capability path with a fixed location prior to the build.
  2. Configure your plugin to use that capability.
  3. Before the plugin runs (after the capability installation is done), make sure you create a symbolic link connecting the fixed path configured before with the new one where your binary will be found.

I hope that makes sense.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events