Scanner command used when applicable (private details masked)
Languages of the repository: Java/XML
Error observed (wrap logs/code around with triple quotes ``` for proper formatting)
Error Details: Report Server [Project Analysis]
Error Message
There was an issue whilst processing the report. Please contact support with the Project Analysis ID: AYscySxrfNe0A8mJ04Dm.
Steps to reproduce
In a maven project execute this command to build jars: mvn clean verify
After finishing the scan submit go to the background tasks page of the scanned project on the SonarCloud and wait a while for the backend task to finish.
Thank you for reaching out. Does this issue persist if you re-run the analysis on the same long branch?
If yes, I would ask you to provide me with your project and organization keys via private message (I’ll ping you there).
There was an issue whilst processing the report. Please contact support with the Project Analysis ID: AYsomX_aQzXlumzKeZLy.
There was an issue whilst processing the report. Please contact support with the Project Analysis ID: AYs7Yqn6U0yiejpNw68T.
There was an issue whilst processing the report. Please contact support with the Project Analysis ID: AYs8Uxqjjvc5iLeDGJN2.
For the project and organization keys of ours, I’ll send them to you via email.
Thanks and looking forward to you reply,
Jesse Hwong
After investigating on your issues, we noticed several things.
The report processing fails because a lot of files have been moved and added to your project since the last successful analysis.
As a record, we have ~5000 files in the database for your project, from the last successful processing, and the latest report came with more than 12000 files.
Many of the files have a high number of lines of code (more than 1000).
Internally, SonarCloud detects the moved files, and the issue you experienced highlighted a bug within our product. We are working on a fix.
In the meantime, and to help you maximize the value you get from SonarCloud, I have some suggestions:
Make sure that no generated code is included in the analysis scope.
Code generators often generate really long files, with a really high number of issues that are useless to see and fix on SonarCloud since this code is usually not meant to be read and updated manually. Here is the documentation to configure the Analysis scope.
I also noticed that in this project, only the main branch is analyzed. At Sonar, we believe in the Clean as You Code methodology, to make sure that all the new code produced by the team matches the quality requirements defined for the project. The first step of this methodology is to analyze the pull requests or short branches of your project. This comes with no additional cost, so I’d suggest having a look at the Clean as You Code methodology page, and at the branch analysis page.
Thanks for your detailed explanation, Claire. We have another question, so, we have both Java codes and public html codes (html, css, js etc) in the same bitbucket repository. We want to scan both, how can we achieve this goal on a single sonar cloud project? It seems that we can only create one sonar cloud project from one bitbucket repository.
No problem at all: our scanner scans all the languages at the same time, so the analysis should contain your Java and your HTML code if the analysis scope is properly configured, without any further configuration on your side.
If you want to have different quality gates for the HTML and Java code, you could have a look at the monorepository feature (ie. how to bind several SonarCloud projects with the same BitBucket repository, with pull request decoration from all of them on the relevant files). Documentation is here.
