Here it is: http://docs.sonarqube.org/display/SONAR/Analyzing+with+SonarQube+Scanner+for+Jenkins
On 8 December 2015 at 10:39, Omertron <[email protected]> wrote: > Hi, this link no longer works, is there an updated one? > > BR > Stuart > > On Wednesday, 18 November 2015 16:48:58 UTC, Duarte Meneses wrote: >> >> The plugin is not deprecated, only the sonar-maven job type. There are >> several ways of running an analysis with the plugin. >> We feel that it is better to use Jenkins' standard maven target (in a >> Freestyle project or maven project) with the new functionality of injecting >> the sonarqube configuration as environment variables. >> This ensures that you do not rely on our adaptation of the maven job, and >> instead use the standard one. >> >> You can find the documentation, with an example here: >> http://docs.sonarqube.org/display/PLUG/Triggering+SonarQube+analysis+on+a+Jenkins+Job >> >> As you can see in the doc, there is no need to change anything in the >> projects, not even in the SonarQube configuration in Jenkins. >> In any case, we do not plan to remove the sonar maven job type anytime >> soon. >> >> >> BR >> >> On Wednesday, 11 November 2015 23:58:06 UTC+1, Jeff Vincent wrote: >>> >>> I recently am seeing this message in my Maven jobs in Jenkins that use >>> the SonarQube plugin: >>> >>> It is no longer recommended to use SonarQube maven builder. It is >>> preferable to set up SonarQube in the build environment and use a standard >>> Jenkins maven target. >>> >>> Is there something explaining this change in detail and what the >>> implications are? The plugin website makes no mention of this that I could >>> see and Googling the above message didn't yield anything of value. >>> >>> Some questions I have include: >>> >>> - Is the plugin being deprecated? >>> - If so, why? >>> - Does that mean each job has to add Sonar to the POM and then run >>> an additional post-build step? (The beauty of the plugin is/was that I >>> didn't need to do that in my 150+ Maven projects). >>> - What additional things need to be setup for SonarQube in the build >>> environment beyond potential changes in the POM files? >>> - Any sample implementations we can use as a guide? >>> >>> Thanks. >>> >>> -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/icysD2FlAXY/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/e147a3c4-0c20-4c88-bbe5-52ddaec5a364%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/e147a3c4-0c20-4c88-bbe5-52ddaec5a364%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- *Duarte MENESES | **SonarSource* http://sonarsource.com -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAC%2BcT%3D%2BVeK_RCcmUPpHvvWjND2cVFt_68pWkETqj8EGqjBXo8Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
