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,467,388
Community Members
 
Community Events
177
Community Groups

Rename Sonar Capability in Bamboo

Intending to rename the capability for the SonarScanner in Bamboo. When changing the name in the capability settings for an agent, the new name is not changed in all build plans that are using the scanner. With many build plans using the Sonar scan task, it is a lot of manual work to make the change, 

1 answer

Hi!

Yes, renaming a capability leads to an inconsistent state in the Sonar tasks. The same happens for the NodeJS tasks, you can follow the ticket here BAM-20531 . Tasks that store the capability/executable in the task configuration will still show the old value after the renaming.

We did not find a reasonable way to mitigate this issue, mainly because we are missing API’s to find tasks based on configuration values.


Thanks for understanding,
Christian - Mibex Software

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events