Closed tlbonds2 closed 5 years ago
simondel
commented
5 years ago Interesting. This is not supported right now as I only look at the first available task report as generated by the sonarqube tasks: https://github.com/simondel/sonar-buildbreaker-vsts/blob/master/extensions/sonarqube/tasks/buildbreaker/common/checkQualityGateTask.ts#L60
This shouldn't cause the specific error that you're getting though... Do you see any logging before you get the error?
tlbonds2
commented
5 years ago Hello! Thanks for reaching out. This is the only detail in the logs:
gt97
commented
5 years ago Hello team. I have the same need indicated by the title of the post. I have a build pipeline with two distinct analysis. As said by Tom in an answer before the result depends only on the first task (alphabetical order) and not on both tasks. Is this featre going to be implemented in the future?
Thanks Gianluca
simondel
commented
5 years ago Hi @gt97 and @tlbonds2 :) This has been added with v8.0.0 of the extension.
Could you try it and out let me know if it works for you?
More info: https://github.com/simondel/sonar-buildbreaker-vsts/releases/tag/SonarQube-build-breaker-8.0.0
simondel
commented
5 years ago Since I didn't hear about any issues, I'm closing this issue for now.
gt97
commented
5 years ago Hi Simon,
thank you for your reply
sorry I came back yesterday from summer holiday. I see there is an issue related with SonarQubePublish introduced by versione 4.7.0 that doesn't publish the results ( https://developercommunity.visualstudio.com/content/problem/694508/the-new-version-470-of-publish-quality-gate-result.html ).
I think the SonarQubePublish has to work properly for testing the sonar-buildbreaker
Thank you again Kind Regards Gianluca
Il giorno dom 18 ago 2019 alle ore 10:45 Simon de Lang < notifications@github.com> ha scritto:
Hi @gt97 https://github.com/gt97 and @tlbonds2 https://github.com/tlbonds2 :) This has been added with v8.0.0 of the extension.
Could you try it and out let me know if it works for you?
More info: https://github.com/simondel/sonar-buildbreaker-vsts/releases/tag/SonarQube-build-breaker-8.0.0
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/simondel/sonar-buildbreaker-vsts/issues/7?email_source=notifications&email_token=AJWABBU3ST25VHHXIZDDT33QFED27A5CNFSM4IGTMFO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4Q3OCY#issuecomment-522303243, or mute the thread https://github.com/notifications/unsubscribe-auth/AJWABBULD37IH5LD3UKYXV3QFED27ANCNFSM4IGTMFOQ .
--
Tel: +39 0522 582839 <+39%200522%20582839> Fax: +39 0522 582859 <+39%200522%20582859>
Via Che Guevara 4 42100 Reggio Emilia www.credem.it http://www.credem.it/
--
P meno carta... più alberi: se non è proprio necessario non stampare questa mail, grazie.
Le informazioni contenute nella presente comunicazione e negli eventuali documenti ad essa allegati potrebbero essere tutelate dal segreto bancario e sono comunque confidenziali e ad uso esclusivo del destinatario sopra indicato. Qualora non fossero a lei destinati, la preghiamo di tener presente che la divulgazione, distribuzione o riproduzione di qualunque informazione in essi contenuti sono vietate. Se ha ricevuto la presente comunicazione per errore, la preghiamo di volerci avvertire immediatamente e di distruggere quanto ricevuto. Con il presente messaggio la scrivente società non intende contrarre obbligazioni o svolgere attività di consulenza o di collocamento e promozione di strumenti finanziari. L'eventuale assunzione di obbligazioni dovrà essere espressamente accettata dalla scrivente società per iscritto o tramite un messaggio che riporti una firma digitale "forte", così come definita dal DPR 28 dicembre 2000, n. 445, art. 10. La Società inoltre, ha adottato un Modello ai sensi del D.Lgs. 231/01 e specifici standard di comportamento per i quali si rimanda alla "Comunicazione standard etici" consultabile sul sito www.credem.it http://www.credem.it/
Grazie per la collaborazione. Credito Emiliano S.p.A.
This message including any attachments contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited, and are kindly requested to return the e-mail to sender and delete this message from your computer. By sending this message, our company does not intend to enter into any legally binding obligation or provide any financial advice or offer to buy or sell financial instruments or make solicitation of such products and services. Our acceptance of legally binding obligation must be confirmed by us either in writing or via e-mail with chriptographically authenticated digital signature and certification of message integrity (so called "firma digitale forte", in accordance to art. 10 of the Italian Decree 28 December 2000, no. 445). Furthermore, the company has adopted a set of regulations as a means of compliance to the Italian legislation D.dl 231/01, as well as a code of conduct which can be viewed on the website www.credem.it http://www.credem.it/ under the heading "Comunicazione standard etici" Many thanks for your kind co-operation. Credito Emiliano S.p.A.
Hello Team, We are using the SonarQube build breaker task 2 times in the same Azure DevOps build pipeline, since we have 2 separate scans configured. So we will scan the webui source code(java) which gets posted to one Sonar project, then later in the pipeline we scan the DB source code, which gets posted to another Sonar project. We would like to fail the build if either quality gate fails. However, with this configuration we get the following error when the second build breaker task executes:
[error]The operation was canceled.
Is this type of configuration supported?
Thanks in advance for the insight! -Tom