You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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,
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