Our site has a single sonarqube server. Our builds have been configured as maven projects, and run the sonarqube plugin as a post build publisher.
Not sure of the rationale for this approach. I have added the sonar:sonar goal to a maven build and get the same result aa jobs that use sonarqube plugin as a separate step. is there a compelling reason that I would want to use the sonarqube plugin instead of running sonar in the primary build? Michael -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/60d2ee44-7019-4372-aa85-2421b32059e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
