Work with pull request
04:22:07.775 ERROR: Caused by: Validation of project reactor failed:
o To use the property “sonar.pullrequest.key”, the branch plugin is required but not installed. See the documentation of branch support: https://redirect.sonarsource.com/doc/branches.html.
o To use the property “sonar.pullrequest.branch”, the branch plugin is required but not installed. See the documentation of branch support:
o To use the property “sonar.pullrequest.base”, the branch plugin is required but not installed. See the documentation of branch support:
Pull Request support requires at least the developer edition of SonarQube. If you don’t want to analyze your pull requests and keep using the community edition, then simply create a second build definition without any SonarQube task, and use it in your branch strategy to build pull requests.
How was it working before SonarQube 7.2 ? If you don’t pass any parameter and let SonarQube analyze your pull requests, it will erase the analysis of the main branch. Were you using any other special configuration or custom plugin to analyze your pull requests without erasing master analysis?
I’ve attached the exact error below. It is slightly different that the error described in the post topic, but I believe I saw another community post that linked to this one. Also, we’ve since downgraded to SonarQube 7.1 and we do not receive the error.
2018-07-06T10:30:39.4725230Z ##[error]10:30:39.461 ERROR: Error during SonarQube Scanner execution
2018-07-06T10:30:39.4761590Z 10:30:39.461 ERROR: Error during SonarQube Scanner execution
2018-07-06T10:30:39.4923090Z ##[error]10:30:39.461 ERROR: Unable to load component class org.sonar.scanner.scan.ProjectLock
10:30:39.461 ERROR: Caused by: Unable to load component class org.sonar.scanner.scan.DefaultInputModuleHierarchy
10:30:39.461 ERROR: Caused by: Validation of project reactor failed:
o To use the property "sonar.branch.name", the branch plugin is required but not installed. See the documentation of branch support: https://redirect.sonarsource.com/doc/branches.html.
2018-07-06T10:30:39.4984940Z 10:30:39.461 ERROR: Unable to load component class org.sonar.scanner.scan.ProjectLock
2018-07-06T10:30:39.5020950Z 10:30:39.461 ERROR: Caused by: Unable to load component class org.sonar.scanner.scan.DefaultInputModuleHierarchy
2018-07-06T10:30:39.5057220Z 10:30:39.461 ERROR: Caused by: Validation of project reactor failed:
2018-07-06T10:30:39.5094090Z o To use the property "sonar.branch.name", the branch plugin is required but not installed. See the documentation of branch support: https://redirect.sonarsource.com/doc/branches.html.
Sorry if I was not clear. Cloud you please enable VSTS debug logs (setting the variable system.debug to true when you queue your build). I’m interested to have the value of all build variables we are relying on to compute configuration (like Build.SourceBranch).
Hi. was there a resolution to this? I’ve recently upgraded to 7.2 and am also receiving the same error as the previous user. We are using the community edition and not passing sonar.branch.name explicitly.
Same problem in version 4.3.2 after update SQ to 7.2.1. How to solve it? Problem is not in TFVC but in TFGIT repository. We want to analyze only one branch without pull request. Before update it works fine after update build failed. What is solution?
Edit: Prepare analysis is 4.3.2 and Run analysis is 4.3.0.
OK, my question could be … How to setup analyze to another branch than master? On master branch analyse works fine but we need setup analyze to developer branch (only one branch). Thanks.
It is very nice support. How it seem in payed version …?
Is there any chance to work with previous version? Our backup admin setup full dayly backup so backup from upgrade is not available. Need help because version 7.2.1 is not usable.
There have been two kinds of error messages mentioned in this thread:
(pull-request related)
And:
(branch related)
Which one are you encountering here ? If latter then as discussed it might worth following-up in this newer thread I mentioned. Specifically in light of your latest notes:
We want to analyze only one branch without pull request
How to setup analyze to another branch than master?
Below note might be insightful:
Which in turns means you cannot perform an analysis on another branch than master (with Git on VSTS ; related code fwiw).
