Scapegoat analysis results not captured in SonarQube about sbt-sonar

[mwz]

Hi @goldsworthy, we're aware of an issue with the scapegoat sensor and multi module projects, which we're tracking in sonar-scala project (sonar-scala/sonar-scala#92). Please keep an eye on this issue - I'm hoping to fix it pretty soon.

[mwz]

Here is the hotfix sonar-scala/sonar-scala#96 - I should be able to release it relatively quickly once the PR gets reviewed.

[mwz]

Hi @goldsworthy, would you be able to give 6.5.1 a try and let us know if that fixes the issue for you?

[goldsworthy]

@mwz I installed the 6.5.1 plugin and tested this with the example project and my own project. I'm not seeing the scapegoat information in SonarQube for either project. Please let me know if there is any other information I can provide.

[BalmungSan]

Hi @goldsworthy, that's strange

Could you provide us with the debug logs of the test project run.

[goldsworthy]

@BalmungSan https://gist.github.com/goldsworthy/44e497fc93d8486884d351a122967123

[BalmungSan]

@goldsworthy I think I found your problem.

If you were using the old scapegoat plugin those rules are no longer valid, since this is a new plugin, so you should update your quality profile.

PS: If you want you can use the default Scapegoat quality profile that the plugin provides, just for testing 😉

Hope it helped 👍.

[goldsworthy]

@mwz @BalmungSan I can confirm this is working properly - your help and responsiveness is greatly appreciated!

[mwz]

That's excellent, I'm glad we got to the bottom of it - thanks @BalmungSan for jumping in!

@goldsworthy, the best thing you can do for now is to create a new profile with scalastyle and scapegoat rules (if you want to use both). In the near future, we're planning to provide both a combined profile (Scalastyle + Scapegoat) along with a recommended profile, so this should be easier to set up.

It also looks like SonarSource will be working on official support for Scala later this year, so watch out this space.