We are using the developer edition of SonarQube with version 220.127.116.11709. Before upgrading we used 18.104.22.168424.
Since the upgrade we don’t get any PR Decoration in Bitbucket anymore (no comments, no report), nor do we see the Quality Gate in the linked builds anymore.
We are using different kind of scanners offered by the Azure DevOps, like the “Integrate with Maven or Gradle” one as well as the “Use standalone scanner” option.
The builds run through smoothly, there is also always “SUCCESS” shown in the background task list and the error log does not show anything wrong.
The picture above shows the current state on the left with 9.5, the right one shows an old PR that was decorated before we upgraded to 9.5.
According to our settings everything still seems fine tho:
Been waiting for a few days now because I was hoping there might be just an issue on Bitbucket - and also was expecting that other people would mention this if it actually is an issue on SonarQube - but since there’s nothing yet and I can’t find anything mentioned in any of the release notes I thought it’s time to open a ticket here, maybe you can help us out - thanks!
Okay, this issue can be closed - sorry:
After further investigation I figured out that we had a plugin with a PostProjectAnalysisTask that threw the following error since the migration to 9.5 (which was only shown with the ‘trace’ log level):
nested exception is java.lang.NoClassDefFoundError: org/sonar/api/i18n/I18n
Fixing the plugin also fixed the PR Decoration.
Any chance you can tell us what plugin this is (assuming it’s an open source plugin, not something you built yourself?) If we need to update our plugin version matrix or report a bug to a maintainer, it would be good to know.
we’re using a fork of a super outdated slack plugin that posts quality gate results to different slack channels, but it’s neither maintained officially anymore nor listed in the SonarQube marketplace
Ah, I know the plugin you’re talking about. Back in my support days, that plugin was known for causing trouble with messing up communication over TLS (due to competing versions of OkHTTP). Good to know it’s now causing trouble in a different way, 3 years later.
Thanks for the follow-up.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.