Thanks Idan, we'll release 2.6.1. 2017-03-22 16:22 GMT+01:00 Idan Adar <i...@adar.me>:
> I can confirm that in my case the updated plug-in now works! > > > On Wednesday, March 22, 2017 at 4:53:16 PM UTC+2, Julien HENRY wrote: >> >> Here is a release candidate fixing the issue with master/slave behavior: >> https://repox.sonarsource.com/sonarsource-public-builds/org/ >> jenkins-ci/plugins/sonar/2.6.1.1212/sonar-2.6.1.1212.hpi >> >> Could you please test it and confirm that it solves your problems? >> >> Thanks >> >> Julien >> >> 2017-03-22 11:19 GMT+01:00 Julien HENRY <julien...@sonarsource.com>: >> >>> Guys, >>> >>> I was finally able to reproduce. Here is the ticket for details: >>> https://jira.sonarsource.com/browse/SONARJNKNS-282 >>> >>> We will release a bugfix quickly for this specific problem. >>> The issue with Gradle will deserve more thinking and a dedicated sprint. >>> BTW there is a workaround (--info) so that's not a blocker issue. >>> >>> Thanks again for your feedback and help to investigate the issue. I will >>> probably ask you to test the bugfix version before releasing it. >>> >>> ++ >>> >>> Julien >>> >>> 2017-03-22 10:23 GMT+01:00 Idan Adar <id...@adar.me>: >>> >>>> To recap, >>>> I've updated the stage to: >>>> >>>> stage ("SonarQube analysis") { >>>> steps { >>>> script { >>>> withSonarQubeEnv('SonarQube') { >>>> sh "../../../sonar-scanner-2.9.0.670/bin/sonar-scanner" >>>> } >>>> >>>> def qualitygate = waitForQualityGate() >>>> if (qualitygate.status != "OK") { >>>> error "Pipeline aborted due to quality gate coverage >>>> failure: ${qualitygate.status}" >>>> } >>>> } >>>> } >>>> } >>>> >>>> It might be that doing this in the same stage it not possible? >>>> This fails with: >>>> >>>> java.lang.IllegalStateException: Unable to get SonarQube task id >>>>> and/or server name. Please use the 'withSonarQubeEnv' wrapper to run your >>>>> analysis. >>>> >>>> >>>> Under SonarQube servers section in the Jenkins settings I have: >>>> Name: SonarQube >>>> Server: http://****:9000/sonarqube >>>> >>>> In the console log I do see: >>>> >>>> INFO: ANALYSIS SUCCESSFUL, you can browse http:// >>>>> ****:9000/sonarqube/dashboard/index/cert-mgmt-dashboard >>>>> INFO: Note that you will be able to access the updated dashboard once >>>>> the server has processed the submitted analysis report >>>>> INFO: More about the report processing at http:// >>>>> ****:9000/sonarqube/api/ce/task?id=AVr1S35oyohgD3UCfaIt >>>> >>>> >>>> The second link has this: >>>> >>>> {"task":{"organization":"default-organization","id":"AVr1S35 >>>> oyohgD3UCfaIt","type":"REPORT","componentId":"AVrnCD3cyohgD3UCfaG0", >>>> "componentKey":"****","componentName":"****","componentQualifier":"TRK" >>>> ,"analysisId":"AVr1S4EhtEGQbCizBv8A","status":"SUCCESS","submittedAt": >>>> "2017-03-22T11:14:09+0200","submitterLogin":"****","startedAt": >>>> "2017-03-22T11:14:10+0200","executedAt":"2017-03-22T11:14:11+0200","e >>>> xecutionTimeMs":473,"logs":false,"hasScannerContext":true}} >>>> >>>> What is missing, other than this being run on a slave (the build >>>> machine used by Jenkins is also the same machine used for the SonarQube >>>> server)? >>>> >>>> >>>> On Wednesday, March 22, 2017 at 10:57:01 AM UTC+2, Julien HENRY wrote: >>>>> >>>>> >>>>> 2017-03-22 9:42 GMT+01:00 Jan Fabry <jan....@thanksys.com>: >>>>> >>>>>> (but it's not always clear to me which >>>>>> ones actually do that, and since which version) >>>>>> >>>>> >>>>> See: https://docs.sonarqube.org/display/SCAN/Analyzing+with+ >>>>> SonarQube+Scanner+for+Jenkins#AnalyzingwithSonarQubeScannerf >>>>> orJenkins-AnalyzinginaJenkinspipeline >>>>> >>>>> It should work for: >>>>> - SQ Scanner 2.8+ >>>>> - SQ Scanner for Maven 3.1+ >>>>> - SQ Scanner for Gradle 2.1+ >>>>> >>>>> It doesn't work currently with the Scanner for MSBuild. >>>>> >>>> -- >>>> You received this message because you are subscribed to a topic in the >>>> Google Groups "Jenkins Developers" group. >>>> To unsubscribe from this topic, visit https://groups.google.com/d/to >>>> pic/jenkinsci-dev/7so6S2mAhzg/unsubscribe. >>>> To unsubscribe from this group and all its topics, send an email to >>>> jenkinsci-de...@googlegroups.com. >>>> To view this discussion on the web visit https://groups.google.com/d/ms >>>> gid/jenkinsci-dev/9fe415f6-4f2c-435f-b77c-8158082818e5%40goo >>>> glegroups.com >>>> <https://groups.google.com/d/msgid/jenkinsci-dev/9fe415f6-4f2c-435f-b77c-8158082818e5%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/jenkinsci-dev/7so6S2mAhzg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-dev+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/6415f21e-3570-4440-b043-0192746d59fa% > 40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/6415f21e-3570-4440-b043-0192746d59fa%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAD9wyxHFi6C5ZgqbtamR0%3D4TXpPd5vgS8q_xiT5YumNb3%3DDNzg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
