Currently, we have SonarQube DE( 7.8) installed and integrated in our build pipeline. In order to protect the in-flight projects, we are planning to install EE SonarQube 9.9 in a separate “temporary” server with a new production key( that we recently got ) for our new project and leave the existing DE SonarQube 7.8 running until the existing projects are complete.
Once the existing critical projects are complete, we are planning to install and set up SonarQube 9.9 EE in our “permanent” environment and decommission the installation in the temporary server.
I would like to clarify whether we would be able to re-use the same license key when we move the SonarQube 9.9 EE from our temporary server to our permanent server.
Would you mind sharing what you want to protect your in-flight projects from?
There are a couple things here. Regarding license for the temporary server, if the JDBC URL changes, then you’ll need a new license key.
But you should be able to just upgrade the 7.8 instance and continue using its license. To be clear, licenses are not version-specific. Your license key should work throughout your upgrade path, which is
Thanks Ann for the response. Please find more details.
Basically, our in-flight projects are using Sonarqube 7.8 Developer edition which is installed on our main server. They are so close to going live. Hence, we dont want to make any changes to the sonarqube or any settings at this stage.
Our new project is on Java 17 and hence requires Sonarqube 9.9.
We recently bought Enterprise Edition license.
Hence our plan is to install Sonarqube 9.9 Enterprise edition with the new license on a temporary server for now which our new project can point.
Later( in about 1 or 2 months time ) move it to the permanent server and at this point all projects ( both existing ane new ) will point to the sonarqube EE 9.9 on the perm server.
Based on your respose, it looks like, we wont be able to do this move. Please can you check if there are any alternatives like the below.
Can we install Sonarqube 9.9 Developer edition on the temporary server so we dont end using up the license. At a later point, we can use the license to migrate from Sonarqube DE 7.8 to Sonarqube EE 9.9?
That’s not quite what I said. You should probably talk to your sales contact about this question of temporary vs permanent servers. And there are two components here: the SonarQube server and the SonarQube database. If you can retain the “temporary” database and adopt it as your permanent server, there’s no need to change the license key.
Alternately, it sounds like your 7.8 server is Community Edition. You can upgrade it to 9.9 and then export the projects from it and import them into your EE instance. That would put all your projects - with all their history - together in the same DB.
But before you go down that road, there’s one more thing you should consider.
I get that you don’t want to disrupt or delay your production release. And what you’re missing in SonarQube 7.8 is not just a lot of UI upgrades. You’re missing a lot, I mean a lot of rule improvements (both removal of false positives and removal of false negatives) and new rules.
Yes, that potentially means new issues raised on your almost-done projects. And I understand if you’re afraid that would disrupt development. But isn’t it better to find out about any potential bugs or vulnerabilities now rather than after you’ve pushed the code out to production?
And in case it matters at all, newly detected issues in the projects’ existing code would be backdated, so they wouldn’t appear in the New Code period.
yes, we will very soon ( in a month’s time ) have Sonarqube EE 9.8 running on main server and all projects ( including existing and new ) will point to it.
Our immediate concern is on how to manage this interim state.
I now understand your point regarding the fact that license would be tied to sonar db instance.
It would be great if you could answer the below query.
Can we have two sonarqube( both db and application ) instances for this interim period
Instance 1 - SonarQube 7.8 DE , perm server DB, perm server
Instance 2 - SonarQube 9.9 DE , temporary DB, temporary server
and very soon( in a month or so ), Instance 1 will be upgraded to 9.9 EE with the new license that we bought recently and instance 2 will be decommissioned
Please can you answer the above query or does this need to be discussed with Sales contact.
No need for the sales contact here. This one I can answer
You can absolutely run those two instances (pointing to two different DBs) side-by-side with no problem. As discussed above, I don’t recommend it. But you can do it.
That was a typo, right? You’re gonna have SonarQube 9.9 LTS EE running, right? Because 9.8 is past EOL, and unsupported. SonarQube 9.9 LTS is the hardened, supported version of 9.8.
We had an internal chat on this topic. We now have a slightly different understanding and approach.
Sonarqube Account contact person had mentioned in their meeting about the concept of Staging and production mode available for Enterprise Editions.
Therefore, we can have 9.9 LTS Enterprise edition installed on the temporary server as a staging set up and at a later point of time, install production mode of 9.9 LTS Enterprise edition on our main server.
Based on the above info, it’s still not clear if the same license key can be used in staging mode( on temporary server and temp db ) as well as in production mode ( on permanent server and prod db) or if we need to request for a separate staging mode license key.
At this stage, we are provided with only one license key from sonarqube and we are not sure if it’s a production license or staging license. If it’s one of them , then we need to request the other. If the same can be used for both production and staging instance, then we dont need a separate key.
