License Expiration

Template for a good new topic, formatted with Markdown:

  • ALM used (GitHub, Bitbucket Cloud, Azure DevOps)
  • CI system used (Bitbucket Cloud, Azure DevOps, Travis CI, Circle CI
  • Scanner command used when applicable (private details masked)
  • Languages of the repository
  • 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/co
  • Potential workaroundde around with triple quotes ``` for proper formatting)
  • Steps to reproduce

Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

We currently have two licenses in our environment: the Developer Edition for on-premise applications and the Enterprise Edition for the cloud.

Both licenses have expired, and we are considering transitioning our on-premise Developer Edition to the cloud by using the Enterprise Edition for both on-premise and cloud environments.

Could you kindly confirm if this switch is feasible and whether we might encounter any issues transitioning from the Developer Edition to the Enterprise Edition?

we use Helm to deploy and I have gone ahead to edit only the edition to enterprise but it still did not change after the update
Best regards,

AA

Hey there @bammy-A

Project Move allows you to consolidate projects from multiple instances (of any edition) onto an Enterprise Edition or Data Center Edition instance of SonarQube Server assuming those instance meet the prerequisities.

Both instances will require valid licenses to achieve this, and it would probably be best that you get in touch with your SonarSource Sales Representative (or contact@sonarsource.com if you don’t know who that is) to coordinate that.