Template for a good new topic, formatted with Markdown:
ALM used (GitHub)
CI system used (Buildkite)
Scanner command used when applicable (Gradle)
Languages of the repository(Mainly Java)
Only if the SonarCloud project is public, the URL
And if you need help with pull request decoration, then the URL to the PR too
Error observed (wrap logs/code around with triple quotes ``` for proper formatting)
Steps to reproduce(Migrate the repo from Bitbucket to Github, all other repos run well except two with “Extra configuration steps required Configure analysis“)
Potential workaround
Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!
Project not found. Please check the 'sonar.projectKey' and 'sonar.organization' properties, \nthe 'SONAR_TOKEN' environment variable, or contact the project administrator to check the \npermissions of the user the token belongs to
The Autoscan service was unable to upload the analysis results to SonarQube Cloud because it couldn’t find or access the project. This typically happens after migrating a repository (as you mentioned, from Bitbucket to GitHub) when the project binding hasn’t been properly configured in the new location.
Since you mentioned that after migrating the repo from Bitbucket to GitHub, the analysis shows "Extra configuration steps required Configure analysis", you need to:
Complete the GitHub Integration Setup
Go to your SonarQube Cloud project settings
Navigate to Administration > General Settings
Ensure the GitHub repository is properly bound to the SonarQube Cloud project
The project key and organization must match between GitHub and SonarQube Cloud
Verify Repository Binding
In SonarQube Cloud, go to your organization
Check that the GitHub repository is visible and properly connected
You may need to re-import or re-bind the project after the migration
Review Automatic Analysis Configuration
Since you’re using Automatic Analysis (Autoscan), ensure it’s enabled for the new GitHub repository
The analysis actually completed successfully up to the report generation stage (analyzed 1282 source files), but failed when trying to submit the results to SonarQube Cloud due to the project access issue.
If you still have problems after completing the GitHub integration setup, let me know.
Hi Ann,
Thanks very much for you reply which helps. Well, there is another question: I’ve created a new enterprise and added a new created organisation bound with Github to the enterprise already. Do I need to add the old one bound with Bitbucket to the enterprise if we won’t use the old one any more? Since we have consumed some scan quote with the old one this month, when I created the enterprise and added the new organisation, the consumed information is not added in the enterprise.
I assume that since the Bitbucket-linked org came first, it has its own, separate license, right? If you’re not going to use it anymore, I think you can just kill it. You’ll (obvs) lose the history in it but you’ve already said you won’t use it in the future.
Yeah, we won’t use the Bitbucket-linked org any more. Is it possible to export or keep the scan result history of the org after killing it? the scan result history could be used for analysis of code quality improvement.