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

SonarQube: Adapt to SonarCloud's changes #11

Closed
schnatterer opened this issue Jul 9, 2018 · 0 comments
Closed

SonarQube: Adapt to SonarCloud's changes #11

schnatterer opened this issue Jul 9, 2018 · 0 comments

Comments

@schnatterer
Copy link
Member

schnatterer commented Jul 9, 2018

Change in SonarCloud for PullRequests in GitHub

if you were relying on the GitHub Plugin, its properties are no longer required and they must be removed your configuration: sonar.analysis.mode, sonar.github.repository, sonar.github.pullRequest,
sonar.github.oauth

The new properties are described here

sonar.pullrequest.base=master
sonar.pullrequest.branch=feature/my-new-feature
sonar.pullrequest.key=5
sonar.pullrequest.provider=GitHub
sonar.pullrequest.github.repository=my-company/my-repo

Does that mean we need to differentiate between SonarQube and SonarCloud now?

Change here
For an example see schnatterer/sonarcloudTest

Also: waitForQualityGateWebhookToBeCalled() should no longer exclude PRs. As they are fully analysed on SonarCloud now (and the PRs are commented via the GitHub/BitBucket integrations of SonarCloud), we can query the QualityGate status, as for normal builds. See
scm-manager.

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

No branches or pull requests

1 participant