A workaround is to have a freestyle job do the sonar analysis and call that
from the pipeline. I'll see if I can jump in and do some work in the
SonarQube plugin though.
On Monday, 27 June 2016 21:54:24 UTC+10, Lionel Orellana wrote:
>
> Some work seems to be happening here:
> https://jira.sona
Some work seems to be happening here:
https://jira.sonarsource.com/browse/SONARJNKNS-213
Thanks.
On 27 June 2016 at 17:57, Antonio Muñiz wrote:
> To get a similar UX for SonarQube when using Pipeline, the SonarQube
> Jenkins Plugin needs to be adapted to Pipeline (i.e. a `sonar` step that
> pre
To get a similar UX for SonarQube when using Pipeline, the SonarQube
Jenkins Plugin needs to be adapted to Pipeline (i.e. a `sonar` step that
prepares the environment and execute the analysis using any predefined
goals (with any predefined options).
On Mon, Jun 27, 2016 at 9:06 AM, Lionel Orellana
Hi,
I have a job where I use the SonarQube plugin option to "Prepare SonarQube
Scanner environment" and then run the sonar maven goal like this:
$SONAR_MAVEN_GOAL -Dsonar.host.url=$SONAR_HOST_URL $SONAR_EXTRA_PROPS
How can I do this in Pipeline? I would image I can Prepare SonarQube
environmen
