I’m using SonarCloud in a Monorepo with GitHub Actions. We have it setup for a couple of months and we keep adding new projects over time.
Since this morning one of our projects (one of the biggest and the oldest in SonarCloud) started showing: The main branch has no lines of code.
This happened after a PR was merged and analyzed this morning but we can’t track any related file or code that could be causing this to happen. The latest task ID is AXkj2knpAnnZhKTG2_2i
There is another topic created by @cesarlino showing the same problem.
We have been using SonarCloud (https://sonarcloud.io/ ) integrated with BitBucket for analyzing our Java project. Today (April 30th), out of the blue, it shows message “The main branch has no lines of code.”. We have other Java/Selenium project which continues to work.
We could not find any change around our Java project or settings which could have caused the issue.
[image]
I would appreciate some help to understand what is happening and fix that.
I just identified that this is also happening, no coverage is reported in any branch:
We recently noticed that coverage is not being recorded for our pipelines:
[Report-Bitbucket]
We are using SonarCloud With Bitbucket cloud.
sonarsource/sonarcloud-scan:1.2.1
sonarsource/sonarcloud-quality-gate:0.1.4
To make sure it wasn’t a problem on our end, I modified some code for a repository which had code coverage information the last time it ran and ran the scan and quality gate against the new branch. I verified that the coverage artifact was being captured in Bitbucket.
** Outp…
Colin
May 4, 2021, 9:18am
4
Hey there.
This should be resolved now.
Hey everybody.
I’ve merged all these threads into one – I hope you don’t mind (I really don’t want to be posting the same answer on 5 topics).
Thank you for the reports. The right team has been notiffied. Kudos to @sylvainhalle for an excellent summary of the issue (and finding what is most likely the root cause).
The workaround he mentions should indeed address the issue temporarily.
When there is a further update on this, we will come back on this thread.