Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.6.1
-
Fix Version/s: 1.7
-
Labels:None
-
Environment:Jenkins, no Maven
-
Number of attachments :
Description
Using the Sonar Plugin for Hudson is a REAL pain in the ass if you don't have maven in the first place. Neither does the automatic setup of Maven work nor does it play well if you already have a custom settings.xml, and and and ...
Sonar is single setup in the build process and should not influence the whole build that much. Starting a full download orgy after the build has already been completed on each build node is far form acceptable. As is entering all information about the project twice, once for jenkins, once for the Sonar plugin.
The plugin should as self containing as possible.
Issue Links
- is duplicated by
-
SONARJNKNS-184
Support for the Sonar .Net Plugins with generated pom
-
Instead of Hudson Sonar Plugin, which for the moment relies on Maven, you can directly use Ant or Sonar Standalone Runner to analyse your project. Hope it can simplify your installation.