Doesn't work with Sonarqube version 8.7.0 #309
Comments
Sonarqube 8.7 removed the concept of the `OrganizationDto` and removed the reference to this class in the `BranchSupportDelegate` interface, so the `CommunityBranchSupportDelegate` implementation has had to update the relevant method signature, therefore making this version of the plugin binary incompatible with older versions of Sonarqube. Alongside this, various webservice endpoints for configuring the global ALM definitions have been moved into the Community edition from the commercial Sonarqube editions, so have been removed from this plugin to prevent the bundled definitions conflicting with the plugin versions. As Sonarqube Community Edition now has direct UI options for configuring Bitbucket Cloud, the relevant endpoints have been introduced for supporting this UI, and the Bitbucket Cloud client used for Pull Request decorating has been updated to use OAuth 2 credential negotiation for authenticating, rather than using the Basic authentication previously used on all requests.
Sonarqube 8.7 removed the concept of the `OrganizationDto` and removed the reference to this class in the `BranchSupportDelegate` interface, so the `CommunityBranchSupportDelegate` implementation has had to update the relevant method signature, therefore making this version of the plugin binary incompatible with older versions of Sonarqube. Alongside this, various webservice endpoints for configuring the global ALM definitions have been moved into the Community edition from the commercial Sonarqube editions, so have been removed from this plugin to prevent the bundled definitions conflicting with the plugin versions. As Sonarqube Community Edition now has direct UI options for configuring Bitbucket Cloud, the relevant endpoints have been introduced for supporting this UI, and the Bitbucket Cloud client used for Pull Request decorating has been updated to use OAuth 2 credential negotiation for authenticating, rather than using the Basic authentication previously used on all requests.
Sonarqube 8.7 removed the concept of the `OrganizationDto` and removed the reference to this class in the `BranchSupportDelegate` interface, so the `CommunityBranchSupportDelegate` implementation has had to update the relevant method signature, therefore making this version of the plugin binary incompatible with older versions of Sonarqube. Alongside this, various webservice endpoints for configuring the global ALM definitions have been moved into the Community edition from the commercial Sonarqube editions, so have been removed from this plugin to prevent the bundled definitions conflicting with the plugin versions. As Sonarqube Community Edition now has direct UI options for configuring Bitbucket Cloud, the relevant endpoints have been introduced for supporting this UI, and the Bitbucket Cloud client used for Pull Request decorating has been updated to use OAuth 2 credential negotiation for authenticating, rather than using the Basic authentication previously used on all requests.
Sonarqube 8.7 removed the concept of the `OrganizationDto` and removed the reference to this class in the `BranchSupportDelegate` interface, so the `CommunityBranchSupportDelegate` implementation has had to update the relevant method signature, therefore making this version of the plugin binary incompatible with older versions of Sonarqube. Alongside this, various webservice endpoints for configuring the global ALM definitions have been moved into the Community edition from the commercial Sonarqube editions, so have been removed from this plugin to prevent the bundled definitions conflicting with the plugin versions. As Sonarqube Community Edition now has direct UI options for configuring Bitbucket Cloud, the relevant endpoints have been introduced for supporting this UI, and the Bitbucket Cloud client used for Pull Request decorating has been updated to use OAuth 2 credential negotiation for authenticating, rather than using the Basic authentication previously used on all requests.
|
Master did work for me with sonar 8.7 and gitlab after fixing the configuration. It is really annoying that SonarSource is doing so much refactoring. I would suggest to change to info to see the message in log file when searching for the problem. |
|
Can confirm , sonarqube at least starts with the plugin from master 👍 |
|
It seems there're still some problem with pull request, got this error when handling pull request (merging to the main branch) |
|
@blueghost1983 this doesn't contain enough information for this to be diagnosed. I suspect you've attempted to target a branch that Sonarqube doesn't actually know about, but without some information as to what parameters you're setting in the scanner, and what branches are currently visible in Sonarqube then I can't do any investigation. |
|
@mc1arke I finally found why I got the error. The default branch in azure devops repo is 'develop', but in sonarqube it is 'master', when pull request merges the branch to the 'develop' branch, the target branch can't be found in sonarqube. The solution is to change the 'master' branch name to same as default branch name in azure devops repo. anyway, thanks! |
|
I was able to add settings on the master branch, e.g. it is displayed in the sonar UI, but when I do this |
|
I'm having the same error on v8.7.0. |
|
It works when building from master branch. |
|
It does indeed work from master and I forked the repo to create a build for automation. |
|
I think the bug mentioned is a pre-existing bug, at least one reported for some non-github VCSs. I do get the error if a PR is targetting a branch other than master (current default branch), but PRs to master work fine. |
|
Hi, Do you know if sonarqube-community-branch-plugin version 1.6.0 work at least with Sonarqube version 8.6.0 please? Regards |
|
it is working on 8.6.1-community, so should be still working on 8.6.0. |
|
Version：Sonarqube 8.7.1+sonarqube-community-branch-plugin-1.7.0.jar mvn sonar:sonar -Dsonar.projectKey=*** -Dsonar.projectName=*** -Dsonar.projectVersion=master -Dsonar.ws.timeout=30 -Dsonar.login=[MASKED] -Dsonar.sourceEncoding=UTF-8 -Dsonar.java.binaries=target/classes -Dsonar.java.test.binaries=target/test-classes -Dsonar.java.surefire.report=target/surefire-reports -Dsonar.test.inclusions=/test/ -Dsonar.exclusions=/test/ --settings=./settings.xml -Dsonar.branch.name=master [ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.8.0.2131:sonar (default-cli) on project ils-parent: Failed to upload report - An error has occurred. Please contact your administrator -> [Help 1] Successful execution without parameter -Dsonar.branch.name=master
|
|
Fixed in 1.7.0 of the plugin |
|
I got crazy with this error due to the Azure DevOps new naming from |
Here is error message.
Plugin version: 1.6.0
The text was updated successfully, but these errors were encountered: