Skip to content
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

#934: Use static report key for non-monorepo Bitbucket decoration #951

Merged
merged 1 commit into from
Sep 6, 2024

Conversation

mc1arke
Copy link
Owner

@mc1arke mc1arke commented Aug 18, 2024

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.
Copy link

sonarcloud bot commented Aug 18, 2024

@mc1arke mc1arke linked an issue Aug 18, 2024 that may be closed by this pull request
@mc1arke mc1arke merged commit 7fb5a56 into master Sep 6, 2024
12 checks passed
@mc1arke mc1arke deleted the issue/934 branch September 6, 2024 18:05
@mc1arke mc1arke mentioned this pull request Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bitbucket integration non compliant to the documentation
1 participant