The following analysis is failing for me: AYahv1qEgOyFzq3Rc5p8 Besides these, it seems like no PR analysis run at all? E.g.: GitHub actions update by basrieter · Pull Request #1683 · retrospect-addon/plugin.video.retrospect · GitHub

Hello Bas, The issue with your project is, that the Project Key contains a colon :. GitHub doesn’t allow to use a colon in their repository names, they automatically replace it with a dash - and we use the repository name as a default Project Key. This means that you probably updated the Project Ke…

I just checked the code and sonar.projectVersion should be supported through .sonarcloud.properties, but isn’t documented as such. I’ll ping our docs team!

That is good to hear! I just merged the changes but still get errors: ID=AYah5PK9-qmZzTSKajtl Perhaps it would make more sense to enable CI analysis using GitHub Actions?

There’s a weird error on the backend. I’m going to flag this for attention – but you can try to switch to CI-based analysis if you want to get it up-and-running right away.

Thanks. I switched to CI for now to get things working (hopefully). Thanks for the fast support.

The CI is working now, but not on external PR’s. As they don’t have the secrets stored in the repository the PR orignated from. What is the preferred way of solving this? EDIT: I think that was the reason I started using the Automatic Analysis.

Hello Bas, I see you created a new post here: [image] Failing analysis ID: AYaoNxdf4aDtPUkTUP2l SonarCloud Yesterday I noticed automatic analysis was nog working. I moved to CI analysis, but that did not really work as I wanted (it did not see any PR specific analysis). …

Hi Peter, sorry about the duplicate post (about the same repo). The initial issue was with the automatic scans. They apparently just stopped a while ago for my repo. So I switched over to the CI build but that does not work for external PR’s. So I moved back to the automatic scanning, as the PR’s …

Hello, Ok thank you for the clarification. I tried to reproduce your issue. I created a fork of your repository on GitHub and imported it on SonarCloud - the Automatic Analysis was successfully executed and results visible in the UI. I created a PR and it was also detected and analysis was execute…

It would be unfortunate to loose all that information. Is there no way to find out what the actual error is beloning to the error ID?

Failing analysis ID: AYahv1qEgOyFzq3Rc5p8

SonarQube Cloud

BasRieter (Bas Rieter) March 6, 2023, 11:35am 13

@Colin Did the backend-team find any issue? I had to move back to automatic analysis, but it still won’t work. See Failing analysis ID: AYaoNxdf4aDtPUkTUP2l - #2 by BasRieter

Topic		Replies	Views
Failing analysis ID: AYaoNxdf4aDtPUkTUP2l SonarQube Cloud autoscan	2	626	March 10, 2023
Cloud analysis of github stopped working SonarQube Cloud	30	809	July 23, 2024
Sonar Analysis on Github and daily analysis on sonar cloud stopped working for all our repos SonarQube Cloud github , autoscan	9	500	September 6, 2023
Analysis not running for 2 weeks :'( SonarQube Cloud sonarqube-cloud	9	981	July 29, 2022
SonarCloud Code Analysis Expected — Waiting for status to be reported SonarQube Cloud sales-team	9	690	July 26, 2024

Failing analysis ID: AYahv1qEgOyFzq3Rc5p8

Related topics