Sonar tasks in cloned plans might behave unexpectedly
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
This problem is related to a third party plugin, and therefore not supported by Atlassian. See Atlassian Supported Plugins for more information.
When cloning a plan with a Sonar task present in a job, some behaviors might seem inconsistent with expectations.
Environment
Inconsistencies have been observed using:
Bamboo 8.1.2
Sonar for Bamboo plugin, version 3.2.1
Diagnosis
When running a build, the task involved can produce an unexpected behavior, or produce unexpected results.
ℹ️ In our scenario, reports were not being branched properly, and instead, new projects were being created for each branch.
Cause
In our scenario, the cloned Sonar task was still using a legacy repository configuration and it was not setting the proper name in the Sonar reports. As a consequence, multiple report projects were being created.
Solution
A quick solution can be to delete the Sonar task and re-create it manually.
We also recommend to contact Sonar for further advice, if needed.
Was this helpful?