Hi @Eddie ,
Thanks for your post. I would need a few clarifications from you to help.
I quickly discovered that this arrangement required external machines (GitLab calls them test runners) to perform the scans.
What do you mean by ‘external machines’? Do you mean machines provided by GitLab to run CI/CD pipelines?
This completely blocks my use of SonarCloud and I’m unable to obtain any value for the service I’m paying for.
Can you clarify which services you are paying for? Do you mean SonarCloud, or GitLab or both?
I’m willing to moving to a different Version Control System but it appears that there is no way within the tool to make this change.
Is there any way to change to a different VCS system? Maybe GitHub or Azure. Without the ability to change VCS systems, there is no value in renewing my subscription with SonarCloud.
I will assume here that by VCS, you mean ALM (GitHub, Azure, GitLab or BitBucketCloud, and still use git as the VCS).
You are correct in that there is no possibility to change the ALM once an organization is bound. The approach here would be to remove the organization and create a new one. If your organization is a paying one and you are within the 15 days trial period, you won’t be charged for the removed organization.
I would also like to ask whether your source code is made of compiled languages or interpreted languages.
If these are compiled languages, then you definitely need a CI/CD that will perform scans on top of your build process.
If these are interpreted languages, then you may want to check if these are languages eligible for automatic analysis, which is available only if the ALM is GitHub. In that scenario, you don’t need any machine to perform scans.