-
-
Notifications
You must be signed in to change notification settings - Fork 528
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitbucket integration non compliant to the documentation #934
Comments
I don't see this issue with Plugin version |
This was an intentional choice in #578, however I wonder if it should be altered to use the static project key for non-mono-repos, and only use a dynamic key when in a mono-repo, given the documentation states |
The Bitbucket decoration is currently using the project key to create the analysis report key, but the Sonarqube documentation states this should be a static value across all projects. To ensure that the Bitbucket `Required report` configuration can be created as per the guidance in Sonarqube documentation, the static key is being used where the repository has not been set as a monorepo.
The Bitbucket decoration is currently using the project key to create the analysis report key, but the Sonarqube documentation states this should be a static value across all projects. To ensure that the Bitbucket `Required report` configuration can be created as per the guidance in Sonarqube documentation, the static key is being used where the repository has not been set as a monorepo.
Describe the bug
I upgraded my old SonarQube to the 9.9 LTA and my quality report keys has changed from
com.github.mc1arke.sonarqube
to the SonarQube project key of my maven project.With the update from the plugin version 1.8.1 to 1.11.0, the static report key was changed to the project key which is not what is stated in the sonarqube documentation : Bitbucket Integration
=> Add a Required report called
com.sonarsource.sonarqube
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The report associated with the PR analysis is expected to be
com.sonarsource.sonarqube
Screenshots
Software Versions
The text was updated successfully, but these errors were encountered: