Continuing the discussion from Not receiving Notification:
We have been monitoring notifications for the last month.
As it was suggested in earlier Thread we should receive notifications when long term branches was analyzed.
But it look like it is not working, even when it is a master or development Branch, which is a long-term Branch in our Organisation.
Hi @miq ,
As mentioned I will discuss with the team today and see if someone can take a further look into this to see if there are some issues which are potentially stopping your team from seeing this information.
There are indeed more business rules for sending email notifications to avoid creating too much noise.
It seems they may be a bit too restrictive.
I’ve created an internal ticket to investigate and come back with a more predictable behavior.
Thank you for your patience,
After further investigation, we could find no misbehavior at the moment.
What we did find, is that the email notifications only include the issues where the creation date is the instant of the SonarScanner execution.
In many cases, this date is changed to reflect the date when the line of code was committed, and all those are not included.
The feedback has been noted in our product management tool for further investigation and refinement by our product team. To be transparent, we are working on many other cool features at the moment, and this topic may not become a priority in the near future.
Have a nice day,
So the conclusion is that the single Developer will not be notified if he pushe changes that does not full fill quality Gate. We have to monitor it manually an Then take action on it.
For this use case, I think the “New Quality Gate status” notification is more appropriate, as the developer will be notified if their changes impact the quality gate of the long branch.
You are totally right that monitoring manually the status to take action is not great.
For this use case, I would suggest updating the command used to run the SonarScanner, to make it wait for the Quality Gate to be computed and fail the build if it doesn’t pass. Coupled with your usual build pipeline failure notification system, every developer will be informed that the last build failed due to a Quality Gate breach.
If you are using the SonarScanner CLI, this is as simple as adding this to the command line:
For the other integrations, I would suggest having a look at the documentation here.
Have a nice day,