New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add SonarCloud reporting to our CI #4187
Comments
This comment was originally posted by @haikalpribadi on 2018-08-09 00:07:19+02:00. I'm not sure which requirement to attach this to, @lolski. Perhaps we should align the requirements on CD, which we haven't done lately. |
This comment was originally posted by @haikalpribadi on 2018-08-11 22:20:49+02:00. The token above is set to this new graknlabs account on SonarCloud, @lolski. (It's new, not the old one Filipe created). I've assigned you as admin, so you should be able to make changes. Basically, I'm trying to achieve what is shown in this page but can't seem to find the documentation on how to do it. There is something similar here, but it's for SonarCube, not SonarCloud (I believe SonarCloud is SonarCube run as a service). |
@haikalpribadi @lolski do you think we still need it? |
## What is the goal of this PR? We have integrated sonarcloud.io with the intention of increasing the visibility of source code health (fixes #4187). The code analysis step is ran in the `build` CI job and the result can be viewed at https://sonarcloud.io/dashboard?id=graknlabs-grakn
This issue was originally posted by @haikalpribadi on 2018-08-09 00:04.
Add Sonar source code analysis report to our CI. You can find the maven command below. I imagine we could just add it to the very end of the build job, before parallelisation happens - just an idea.
The text was updated successfully, but these errors were encountered: