#934: Use static report key for non-monorepo Bitbucket decoration #951
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.