Closed mvossi closed 7 years ago
Workaround: I've added
-DsonarRunner.dumpToFile=sonar-dump
as additional Maven command line parameter and it works now.
I just wanted more background information and was very surprised that it ran through. I can easily live with an additional log file for each build. I also retried without this parameter and it failed, adding the parameter and it worked like a charm.
Actually TC SonarQube plugin does nothing with maven sonar:sonar target. Could you send me build logs (failed and passed) to andrey.titov@jetbrains.com?
On Fri, Jul 29, 2016 at 11:34 AM, Vossi notifications@github.com wrote:
Workaround: I've added -DsonarRunner.dumpToFile=sonar-dump
as additional Maven command line parameter and it works now.
I just wanted more background information and was very surprised that it ran through. I can easily live with an additional log file for each build. I also retried without this parameter and it failed, adding the parameter and it worked like a charm.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JetBrains/TeamCity.SonarQubePlugin/issues/25#issuecomment-236125145, or mute the thread https://github.com/notifications/unsubscribe-auth/AETt8GMEmV9Pc0xVoZexcUFPqFVFnFg4ks5qabshgaJpZM4JXZtG .
Andrey Titov Software Developer JetBrainshttp://www.jetbrains.com The Drive to Develop
Okey, the -DsonarRunner.dumpToFile=sonar-dump
parameter actually makes SonarQube Runner skip sending data to the server so currently sonar:sonar step does nothing - it just reads the project structure and dumps it in a file. Could you please check Maven sonar:sonar build step with sonar.login and sonar.password additional parameters works when SonarQube Runner step is disabled?
Haha, that explains a lot :-) OK, here are the results you've requested:
So, as a workaround, I supply these command line parameters and it works.
BTW: Actually, I'm not passing the real PW, but instead use the encryption that was added with the latest Sonarqube release (but that doesn't seem to make any difference in the results I've listed).
Sorry for late reply, I'm on vacation at the moment.
at last , how to dissolve it
For clarification: This is/was a problem of the Sonar-Maven-Plugin, not of SonarQubePlugin for TeamCity. Make sure to supply sonar.login and sonar.password as command line parameters for the Maven plugin (as documented).
Make sure TeamCity 10.x runs with latest SonarQubePlugin for that version. This plugin is configured within TeamCity itself (create separate build step) and doesn't require any Maven configuration. Anyway, you have to provide username and password in the TC-SonarQubePlugin settings GUI, too.
Tested on TC 10.0.1, TC Sonar-Plugin Build 105, SonarQube 5.6.1, Sonar-Maven-Scanner 3.1.1
I've installed TeamCity 10.0 and SonarQube 5.6.1 with the TC10 sonar-plugin.
When I execute the maven goal "package sonar:sonar", I get the following error:
When I enter these additional maven parameters to the build step:
I see the following error: