We have recently moved from SonarQube to SonarCloud to take advantage of the many features this version provided. Especially PR and branch analysis.
Our project is a NodeJs + Typescript service. We have our repository on Github and we run CircleCI to build and run our tests. We have a combination of Unit and integration tests, which we run before calling the SonarCloud step using the SonarCloud orb version 2.0.0.
For the most part works good, however the PR analysis does not leave a summary comment unless we enable the GitHub action.
We had the Github action running on build, which left the summary comment in the PR, however this is redundant since we run the scan also on CircleCI pipeline. Also, the Github summary comment lack the coverage that was later gathered by the sonar CircleCI pipeline step.
Note that we have the sonar-project.properties file for this same reason, we only have the coverage generated on the pipeline and is not pushed to the repository or uploaded anywhere else.
Our sonar-project.properties has but a few properties set:
sonar.projectKey=**our project key**
#--- SonarQube server properties
# --- Project properties (https://docs.sonarqube.org/latest/analyzing-source-code/analysis-parameters/)
sonar.exclusions=src/**/**.spec.ts, src/**/**.test.ts, src/**/*.snap, src/test/**/*
# Encoding of the source code. Default is default system encoding
I’ve also tried adding the following properties dynamically prior to run the scan:
I hope this time the cavalry won’t be late
Could you please share the full GitHub actions workflow file here?
I’ll also contact you in a private thread to get some private information to help with the investigation.
Could you confirm when you started to see that problem? Did you ever have the summary working, and it stopped, or did it never work for you?
Also, at this precise moment, there are 2 incidents happening, one on the GitHub side and one on the SonarCloud side (happening since yesterday morning CET) that could also be impacting you, the timing information will help me figure out if it is the same issue or not at all.
I mentioned that out Github action is to be discontinued because we rely on CircleCI to run our tests and provide the coverage. So having the Github action running is redundant.
In terms of timing, we have just recently started using SonarCloud, and on Monday the Github action was sort of working (with no coverage though). The CircleCI pipeline was never updating the pull request.
We can put this on pause until this incidents are gone and retry right after and if its continuing we can review the configuration. What you think?
I’ll appreciate you can provide me with some status page or similar I can check to see if the incident is solved.
The Pull request incident on SonarCloud started yesterday morning CET, I suspect you may be quite unlucky on this one.
We are implementing the fix at the moment, and it should be fixed in the coming hours.
If it works for you, sure, let’s resume the investigation once they are fixed. You can follow the progress here: https://sonarcloud.statuspage.io/
or here: Azure DevOps PR decoration incident
The title mentions Azure DevOps but it seems to be wider than just Azure.
If I understood correctly, your target is to use Circle CI, so I suggest we focus on having this solution working? Have you followed our in-product tutorial specific to Circle CI to configure the build, with coverage and everything?
You can access it in SonarCloud, and click on your project. On the left bar, click “Information”. On the left column of the page, at the very bottom, click “Check analysis method” and then choose the “Circle CI” tutorial.
It would be great to update the status page though. At the moment, it says that the Github integration is operational so I took some time trying to figure out why it stopped working on our end before I finally found this thread.
Also experiencing the same issue on our projects. If that can help, this occurs only on the projects which are not directly bound to github (for instance this one is not working anymore but that one still is).