xebialabs-community / xlr-sonar-plugin

Integration between XL Release and SonarQube
MIT License
0 stars 1 forks source link

Used SonarQube metric blocking_violations doesn't exist #3

Open AdTromp opened 7 years ago

AdTromp commented 7 years ago

This plugin uses the SonarQube metric blocking_violations. But as far as I am informed the metric is blocker_violations (see: https://docs.sonarqube.org/display/SONAR/Metric+Definitions)

xxxxx_violations Number of issues with severity xxxxx, xxxxx being blocker, critical, major, minor or info.
jdewinne commented 7 years ago

Which version of SonarQube are you using? The current implementation of that tasking is using an older api call. So it should be refactored in order to be compliant with the newer SonarQube api.

AdTromp commented 7 years ago

Hi,

SonarQube 5.6.3

XLRelease 7.0.1

xlr-sonar-plugin-1.2.0

We have always used blocker_violations in our api calls, als in Sonar 4.x.x

Best regards, Ad Tromp Software Development Consultant [APG] APG | ICT | SU ReBLI | RB Portfolio I Oude Lindestraat 70 | 6411 EJ Heerlen T. +31 (0)45 57 91322 ad.tromp@apg.nlmailto:ad.tromp@apg.nl | www.apg.nlhttp://www.apg.nl/

[LinkedIn]http://www.linkedin.com/company/apg [Facebook] https://www.facebook.com/APGcareers APG verzorgt pensioenadministratie, vermogensbeheer, communicatie, bestuursadvisering en inkomensverzekering.

Van: Joris De Winne [mailto:notifications@github.com] Verzonden: woensdag 16 augustus 2017 18:01 Aan: xebialabs-community/xlr-sonar-plugin CC: Tromp, AHMJ (Ad); Author Onderwerp: Re: [xebialabs-community/xlr-sonar-plugin] Used SonarQube metric blocking_violations doesn't exist (#3)

Which version of SonarQube are you using? The current implementation of that tasking is using an older api call. So it should be refactored in order to be compliant with the newer SonarQube api.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/xebialabs-community/xlr-sonar-plugin/issues/3#issuecomment-322818999, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AdoQGT7o0yTCZm6jzYN8CsSvwepMN7BPks5sYxJLgaJpZM4O408g. De informatie in dit e-mailbericht is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Wanneer u dit bericht per abuis ontvangt, verzoeken wij u contact op te nemen met de afzender per kerende e-mail. Verder verzoeken wij u in dat geval dit e-mailbericht te vernietigen en de inhoud ervan aan niemand openbaar te maken. Wij aanvaarden geen aansprakelijkheid voor onjuiste, onvolledige dan wel ontijdige overbrenging van de inhoud van een verzonden e-mailbericht, noch voor daarbij overgebrachte virussen.

APG Groep N.V. is gevestigd te Heerlen en is ingeschreven in het handelsregister van de Kamer van Koophandel Limburg onder nummer 14099617

The information contained in this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you have received it in error, please contact the sender immediately by return e-mail; please delete in this case the e-mail and do not disclose its contents to any person. We don't accept liability for any errors, omissions, delays of receipt or viruses in the contents of this message which arise as a result of e-mail transmission.

APG Groep N.V. is registered in the trade register of the Chamber of Commerce Limburg, The Netherlands, registration number: 14099617