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