I want to upgrade SonarQube and I haven't done this before so I have few question. Please could you help me with them?
How can I find which edition is installed on my server?
How can I find if the installed version is licensed or not?
How can I upgrade from 5.6.4 to 6.7 LTS? Do you have upgrade guide for the same?
You can always find which version is installed by logging into the SonarQube web app and looking at the footer of the page or by going to Administration / System / System Info. If you for some reason can't log in to the web app, and installation folder name does not contain the version number as it does by default, look in the "lib" folder for a file that looks like "sonar-application-6.3.1.jar". That will tell you the version number as well.
Here are the general steps for upgrading, from the Upgrade the Server docs:
Download and unzip the SonarQube distribution of your edition in a
fresh directory, let's say $NEW_SONARQUBE_HOME
Manually install the
non-default plugins that are compatible with your version of
SonarQube. Use the Compatibility Matrix to ensure that the versions
you install are compatible with your server version. Note that the
most recent versions of all SonarSource code analyzers available in
your edition are installed by default. Simply copying plugins from
the old server to the new is not recommended; incompatible or
duplicate plugins could cause startup errors.
Update the contents of
sonar.properties and wrapper.conf files (in
$NEW_SONARQUBE_HOME/conf) with the settings of the related files in
the $OLD_SONARQUBE_HOME/conf directory (web server URL, database,
ldap settings, etc.). Do not copy-paste the old files. If you are
using the Oracle DB, copy its JDBC driver into
$NEW_SONARQUBE_HOME/extensions/jdbc-driver/oracle
Stop your old
SonarQube Server
Start your new SonarQube Server
Browse to
http://yourSonarQubeServerURL/setup and follow the setup
instructions
Analyze your projects (and compute your
Views|Portofolios|Application if you own the Enterprise Edition
product) to get fresh data
Before embarking on this, you will want to check out the intermediate upgrade notes for each version in order: 6.0, 6.1, 6.2, 6.3, 6.4, 6.5, 6.6, and 6.7.
Note that upgrade notes for versions after 6.7 are hosted at the new documentation site.
Related
We upgraded from SonarQube 5.6 to 6.7.2 and also manually upgraded the plugins, including SonarPLSQL from 2.8 to 3.2.0
We are using the community version but have a valid (paid) licence for the plugin. When trying to start we get the error:
org.sonar.updatecenter.common.exception.PluginNotFoundException: The plugin 'license' required by 'plsql' is missing.
When removing the plugin from the plugins-folder SonarQube starts without problems.
Can you please help us?
The way licenses work have changed in the latest LTS. This is why you've got this error.
As you have a valid license of the PLSQL plugin, this means that you are a SonarSource customer so you should get in touch the SonarSource Sales representative you are in contact with to sort this out.
I get this error when trying to look at available packages in Red Hat JBoss Central. This seems to be because of some missing files on the update site.
How did you install devstudio 10.3?
Into your own Eclipse (from update site, from Marketplace, from zip), via rpm, or via installer jar? If into Eclipse, which package (JavaEE, Java, C/C++, etc.) and which source did you use?
Are you behind a firewall/proxy? What OS are you running? Which version of JDK are you using?
Just tried to install everything from Central from devstudio-10.3.0.GA-v20170218-1636-B94-installer-standalone.jar installation on Fedora 24 and it works for me.
I am a teamcity developer and our organisation currently uses Team-city 9.0.3 Free version. Now we maxed out Builds. So we are planning to take an enterprise edition.
But before that we need to upgrade the teamcity to latest version 10.x. while i am doing the upgrade it throws the following error.
Please click the link to see the error
The steps i did for the upgrade are
-- Take a back up of entire Teamcity which will be in /root/.BuildServer/backup
-- Stop the Teamcity server and delete the whole teamcity directory
-- copy the backup .Zip file into import section.
-- download the latest teamcity and do the necessary configurations and start the teamcity server.
-- go to Administration/Import and start importing the file from /root/.BuildServer/import
While importing i am getting the above error as version is not supported.
Please help me on this so that i have to upgrade the Teamcity and go for enterprise edition
Thankyou in advance..
It sounds like you are trying to import a backup created with TeamCity 9 into TeamCity 10, that isn't supported, backups can only be restored with the same version they were created with.
When you install TeamCity you usually have a data directory (probably ".BuildServer" in your case) and the software in a different location. You shouldn't delete the data directory, you should upgrade the database and data directory in place (TeamCity will prompt to do this when the new software starts, refer maintenance mode below).
If you continue with your proposed route you'll need to create a fresh TeamCity 10 database with the new schema version, however you'll loose all the other settings and data as that backup sounds like a project config only backup.
JetBrains provide detailed guides to perform upgrades:
https://confluence.jetbrains.com/display/TCD10/Upgrade
https://confluence.jetbrains.com/display/TCD10/TeamCity+Maintenance+Mode
I just install meteor.js and try to use it replace the old frameworks.
The issue is:
On my windows 10 64bit system, the meteor is use 32bit mongodb(2.6.7), which is limited th database size is 2gb.
How to make the meteor work with 64bit mongodb?
Having researched this myself just now, it looks as though the Meteor version 1.4 release will be updated to version 3.2 of MongoDB, in which "32-bit binaries are deprecated"
Github ticket for the updating of MongoDB
MongoDB declaration that 3.2 has deprecated 32-bit binaries
Meteor 1.4 announcement
If upgrading your MongoDB instance is mandatory now, then unfortunately it looks like the only way is to manually upgrade the binaries yourself. If you do this, I would suggest you make a backup of them just in-case it messes up.
To upgrade to version 3.2 you first need to upgrade to version 3.0, then you can upgrade to version 3.2
I guess you didn't install the right version of Mongo if you have a 32 bits version.
check out their installation guide:
https://docs.mongodb.org/manual/tutorial/install-mongodb-on-windows/
First download the right 64 bits version for Windows:
https://www.mongodb.org/downloads#production
and follow the instructions:
Install MongoDB
Interactive Installation 1 Install MongoDB for Windows. In Windows
Explorer, locate the downloaded MongoDB .msi file, which typically is
located in the default Downloads folder. Double-click the .msi file. A
set of screens will appear to guide you through the installation
process.
You may specify an installation directory if you choose the “Custom”
installation option.
NOTE These instructions assume that you have installed MongoDB to
C:\mongodb. MongoDB is self-contained and does not have any other
system dependencies. You can run MongoDB from any folder you choose.
You may install MongoDB in any folder (e.g. D:\test\mongodb).
Running on Windows Server 2008 R2 with Windows 7 client.
I downloaded and installed VisualSVN Server 2.5.2 without a problem. The page here indicates that this is built against Subversion 1.7.2.
I downloaded and installed TortoiseSVN 1.7.3 without a problem. The page here indicates that this is built against Subversion 1.7.2.
Now I would like to install ankhsvn for use with Visual Studio 2010. The latest version is 2.3.10509 and the page here indicates that this is built against Subversion 1.7.1.
Does anyone know if this will run correctly against my SVN server? Or do I need to wait until ankhsvn release a version built agains SVN 1.7.2? If I need to wait, how promptly do ankhsvn releases usually appear?
Source control is obviously critical so I don't want to risk losing any data by "just trying it".
Subversion versioning requires clients to have the same minor version. So any 1.7.X client should be compitable with every other 1.7.Y client.
For the server, any 1.X client will work with any 1.Y client.
Of course it's a good idea to keep things as up-to-date as possible, but you're not risking anything by combining 1.7.1 and 1.7.2.
The release of AnkhSVN based on 1.7.2 will be out in the coming days, the daily builds are already using this.
From what I'm aware of, we had to upgrade SVN on our servers to be compatible with the latest version of ankhsvn. It was a big deal, for the leads let us know we couldn't use ankh until we updated.
We are also using Tortoise.
Hope that helps.