If you deleted the project, then associated tasks were deleted as well.
You will need to re-submit an analysis to SonarCloud and then see again what the outcome was
I hope this helps
Apologies for not getting back to you earlier. No, I could not find the reason why you got this error. I could see there are other projects in your organization that are successful: maybe an approach would be to compare how they’re set-up on both the :sonarcloud: and Bitbucket sides?
HI @AlxO , There is no difference in the setup when compared to other projects.
I deleted the project and added back, But there is no change in the analysis.
What are the other reasons why Sonar Cloud always returns
Changing the project key (and then updating the pipeline to use the new key) is a workaround for that issue, as found in this other thread. Could you please try that? We are still investigating for the root cause.
If the problem reappears after changing the key, could you please give us:
the full scanner log of the first time the error appears
the new project key
the background task ID
the submission time
any information of something that happened to the project or to the organization: manual deletion of a branch? of the project ? of the organization? an analysis failing for another reason just before? the time since the previous analysis of the impacted branch/ of the project ?..
Thanks a lot, and my apologies for the long time this investigation is taking.
Claire
In good news – we’ve finally tracked down the tricky bug that’s causing this. It could happen when a project was created, a branch analyzed (and that analysis failed), and the project gets deleted/recreated. This caused some orphan database entries that cause the “Compute Engine task main component key is null” error.
Our plan is to stop new cases from occurring, and clean up existing orphans. The work is ongoing.
Great !!! When can we expect this to be available.
We are blocked right now every time we do an Analysis it always return " Compute Engine main Component Key is. null"
Have you tried the workaround I suggested above, to unblock you?
Changing the project key (and then updating the pipeline to use the new key) is a workaround for that issue, as found in this other thread. Could you please try that? We are still investigating for the root cause.