I’m afraid I’m yet someone else who’s analysis is failing and I’m pulling my hair out trying to work out why. It started doing so a few months ago and I’m not sure what changed. In desperation I’ve deleted the project in SonarQube Cloud and re-created it, but I still get this message that analysis failed, with no hint as to why.
On main branch:
Last analysis failed
Analysis ID “739cd7c7-80aa-4909-ae7c-4bb041511949”
The last analysis has failed. If it keeps on failing after several attempts, please contact us on Community forum and provide the following failing analysis ID: “739cd7c7-80aa-4909-ae7c-4bb041511949”.
On a new branch:
Last analysis failed
Analysis ID “AZTQ34HvNKGET2PnpSan”
The last analysis has failed. If it keeps on failing after several attempts, please contact us on Community forum and provide the following failing analysis ID: “AZTQ34HvNKGET2PnpSan”.
ERROR: Wildcards ** and * are not supported in "sonar.sources" and "sonar.tests" properties. "sonar.sources" and "sonar.tests" properties support only comma separated list of directories. Use "sonar.exclusions/sonar.inclusions" and "sonar.test.exclusions/sonar.test.inclusions" to further filter files in "sonar.sources" and "sonar.tests" respectively. Please refer to SonarCloud documentation for more details.
Thanks for letting me know. I appreciate you looking into this.
Just for the future:
It would be invaluable to have that sort of error coming through the sonarqube cloud interface, to aid debugging. I found the line about wildcards in the docs eventually, but it wasn’t obvious. It’d save you some time and effort too!
There is some confusion, at least for someone like me coming to this with little experience with sonar tools, between the different config files, what they do and don’t support and which sonarqube product uses them.