I am getting permissions related errors in my analysis because the process is requesting write access. Before the analysis task starts, if I uncheck the read-only box for the source folder the error does not happen. That is why I'm looking for this fix -
https://jira.sonarsource.com/browse/SLVS-1122
According to the commends on that link, SonarAnalyzer for .Net 1.21 wasn't released until at least Jan 30th. Will this fix be in SonarQube 5.6.6, or will I have to wait until 5.7?
edit: currently running version 5.6.4 through TFS 2015 onprem
You're mixing apples and oranges. The fix you want is in the most recently released version of SonarC#. You can upgrade it in your SonarQube server (mostly) independently of your SonarQube server version.
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 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.
We are trying to upgrade our current SonarQube from 5.6.3. to 6.7.1
We have upgrade our SQL Server to 2014 and 5.6.3 has been tested and it has been working fine when I try to start the 6.7.1 server. It shows the Warning database needs an upgrade but the process seems to be running.
Is the issue because of the plugins which we are supporting or the version of database. I am attaching all the logs that got generated.
Database version : Microsoft SQL Server2014(MSSM studio 12.0.5207.0)
Plugin version :
SonarJava : sonar-java-plugin-4.6.0.8784
C# : sonar-csharp-plugin-5.10.1.1411
Does plugin version has to play any role ( I doubt as it is highly unlikely)
Let me know in case any further details are required.
Please advice.
Thanks in Advance!
It sounds like you're missing the step where you have SonarQube upgrade it's own database schema. Specifically, navigate to [your SonarQube URL]/setup and click the button on that screen. That triggers SonarQube to make the database changes required to support your new version.
In our Sonar Build Environment we use SonarQube Server Version 5.6.6 (64-Bit) and our analysis runs on a Sonar Client Build Operating System with Ubuntu 14.04.5 LTS (64-Bit).
Recently I have upgraded SonarQube from 5.1 to 5.6.6 (LTS). But under "Project Code" the "Customize ON|OFF" option is now missing.
Currently I can see only these options:
Lines of Code
Bugs
Vulnerabilities
Code Smells
Coverage
Duplications
In SonarQube version 5.1 I was using the "Customize ON|OFF" option to customize and add required columns.
How can I enable this feature back in SonarQube 5.6.6?
The feature does not exist any longer (it has been dropped when rewriting the Project space), and there's currently no plan to reintroduce it.
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.