Not that I know of.
We were doing that for hundreds of jobs at my previous job. (On freestyle
project, as the native maven project isn't recommended by many of us).

Just beware to do one normal execution, then one with sonar:sonar as stated
the sonarqube doc.

Le 13 sept. 2016 3:17 PM, "Michael Giroux" <mlgir...@gmail.com> a écrit :

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.

-- 
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/CANWgJS60KCygWa8DTTH0uVxYNKNotn43dpv2h2v-kniCCLbt5g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to