We would like to upgrade our Sonar setup to 6.x but waiting for LTS release. Is there any update on when Sonarqube LTS (6.x) release is scheduled?
Also, we would like to understand major differences between Sonarqube 4.5.7 & Sonarqube 6.x in terms of support for Java/maven/msbuild/fxcop versions and other major features that 4.x users should be aware of.
The release of 6.7 LTS is planned for this fall. But you cannot upgrade directly from 4.5.7 to 6.7; you must first go through the intervening (current) LTS: 5.6.6.
For a summary of the differences between 4.5.7 and 5.6.6, see this blog post. If you want more details, you should consult the release notes, as Simon noted in the comments.
When you upgrade to 5.6.6 (why not go ahead & get that out of the way?), you'll find that your custom dashboards are still there, but have been set aside in favor of a hard-coded project homepage. When you get to 6.7, you'll find that custom dashboards have been eliminated entirely, and a new projects page has been provided, as well as a reworked Measures space and countless other improvements.
Nov 2019 Update: The current LTS is now 7.9. More information about the SonarQube LTS model is available here.
Related
I want to upgrade my ES cluster(current version: 7.6.2) to the latest version (7.15.2 until now)
Is it ok to upgrade directly to the latest version or should I upgrade with 2 or 3 steps on different version?
For instance, for upgrading mongo db, it should be upgraded step by step to the next version...
I just want to know what is the policy or even best practice for upgrading ES ?!?
Thanks
It's totally fine to update between minor versions (7.x -> 7.y) as well as one major version up from latest minor version (6.8 -> 7.y), see upgrading document for the details. Best of all, it can be a rolling upgrade so you can upgrade nodes in the cluster one by one without cluster downtime or data loss. Just make sure cluster health is green before moving on to the next node.
How can I download the user docs/documentation/manual for older ElasticSearch for offline usage?
Recently, the online documentation for older versions of ElasticSearch (for example, ElasticSearch 1.3.2) started to show this message:
WARNING: Version 1.3 of Elasticsearch has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
What worries me most is the may be removed part. Right now, we don't have the resources to upgrade our software to support the latest ElasticSearch version, so we will need to keep working with the older versions for a while. How I will be able to give maintenance to our software if the Elastic company decides to remove the documentation for older versions of ElasticSearch? There is any way to download it from https://www.elastic.co/ or build it from some repository?
Thank you very much for your help!
You can clone the official elasticsearch repository to a local machine, change to branch to the version you want, in your cause branch 1.3, then you will have the documentation in the directory docs.
The documentation is in the .asciidoc format, you can try build it following the official instructions, or using other asciidoc to pdf/html converters.
We launched sonar 4.5.4 in one of our application. Then, we have upgraded sonar with 6.7.5 version and we have got different results.
e.g.: the rule DLS_DEAD_LOCAL_STORE. When we passed our code with 4.5.4 version, this critical rule was not broken at all. With the new version, it appears as a new critical bug even when no changes have been implemented (last commit for this classes was made more than one year ago).
Is there any documentation about rule implementation changes per versions?
Does anyone any experience with this?
When you upgrade SonarQube you have to prepare yourself for some (big) changes. There is a large gap between 4.5.4 and 6.7.5 so, do not be surprised that checkers have been enhanced and severity revised.
It is normal and you should analyze changes before performing any application upgrade.
I'm trying to update Sonarqube usage to the latest LTS Community version, which at present is version 6.7.5. Prior to the upgrade I have been using sonarqube 5.4 and the Github plugin, and with these when we make Github pull requests the Sonarqube analysis runs in "preview" scan mode and makes comments on the pull request for any issues the scan finds. This setup is largely following this pattern.
However, with the upgrade to 6.7.5 this same flow is no longer working. The Github plugin
"is deprecated, and its functionality more than replaced by the
Developer Edition."
I understand that the Developer version of Sonarqube has pull request commenting built-in, but I have a strong preference to continue using the Community version due to the cost differences. Essentially, something that was once free and part of the open source version seems to have been removed or broken in the latest free and open source version because a similar paid option now exists. So I am trying to find a way to preserve the previous Community version usage with the latest Community Sonarqube version. 6.7.5 Community version runs the Github plugin (even though it the plugin is deprecated), but so far I have been unable to get things to make comments on the Github pull requests.
Is there a combination of parameters/plugins that will allow my 6.7.5 Community version of Sonarqube to analyze and make comments on a Github pull request?
These may be relevant:
https://community.sonarsource.com/t/after-upgrade-to-sq-6-7-5-target-sonar-issues-report-issues-report-light-html-is-not-produced/1921
https://jira.sonarsource.com/browse/SONAR-9770
https://community.sonarsource.com/t/preview-mode-ignored/1234
I believe in my case the issue was that after upgrading the rule sets changed, so the rules I initially thought were being used with 6.7.5 were not in fact being applied. This gave the impression that Sonarqube was not commenting on the pull request and led to my question. But after enabling the rules appropriately I was able to see it comment on GitHub pull requests as expected. So this appears to be a case of user error!
Just found a bug regarding "Do not include complexity of nested functions into nesting one complexity".
https://jira.sonarsource.com/browse/SONARJS-729
It say's its fixed with version 2.15 in sonarsource. But i'm unable to find in what version of SonarQube, the same is fixed. Right now, we use SonarQube version of 4.5.6, but the issue still persist in that version.
SonarJS 2.15 is not compatible with SonarQube 4.5.6: since version 2.14, SonarJS requires SonarQube 5.6 or later.
You need to first upgrade to SonarQube 5.6 or later, and then upgrade SonarJS.