[ 
https://issues.jenkins-ci.org/browse/JENKINS-11267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=162628#comment-162628
 ] 

Sedat Guclu commented on JENKINS-11267:
---------------------------------------

Hi, 
Is there a chance to see this case taken into account in a future release?
                
> no (easy) way to make a sonar analysis on maven released version
> ----------------------------------------------------------------
>
>                 Key: JENKINS-11267
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-11267
>             Project: Jenkins
>          Issue Type: Improvement
>          Components: sonar
>    Affects Versions: current
>            Reporter: Sedat Guclu
>            Assignee: sonarteam
>
> There is no way to invoke the sonar plugin on a new maven released version 
> (from freestyle/maven jobs, and even from the m2 release plugin): the sonar 
> plugin uses the pom file found for the previous job steps and not the 
> "released" one ( found in target/checkout by default). Even -f or --file 
> parameters on sonar plugin config are ignored because they are set after the 
> previous one, and perform's "checkoutDirectory" cannot be set on the 
> workspace dir.
> It is very annoying because, in my organisation, we want to set release job 
> templates with automatic sonar invokation on the released version on a same 
> job (which, in my mind, is an absolute need for customer delivered 
> components). The generate report shows then the "next development" version in 
> sonar. Additionally, we do not want to put sonar configs in pom or other 
> because the sonar instances' configs are better centralized then in jenkins.
> The only (VERY ugly) workaround I found was to use the M2 extra steps plugin 
> and override the workspace's "root" pom by the released one before the sonar 
> invokation... 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to