hmm okay i think this was already reported in this community thread. when you are not on the main branch using a yml config it is assumed that you want to analyze this branch, so the property is set here. in the thread i linked is a workaround for this issue
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Azure DevOps task version 5 fails for sonar.branch.name | 4 | 287 | February 22, 2024 | |
Sonarqube 8.9 to use sonar.branch.name | 5 | 2954 | August 10, 2022 | |
SonarQube 7.5 error with Azure DevOps Task fails on other branches "sonar.branch.name" | 2 | 822 | November 14, 2023 | |
Sonar.branch.name error in 6.7.5 LTS | 5 | 2729 | December 10, 2018 | |
Error: To use the property "sonar.branch.name" and analyze branches | 17 | 40487 | July 24, 2020 |