sonarqube5.3

Duplicate key error post SonarQube 5.3 upgrade

北城以北 提交于 2020-01-07 05:00:29
问题 We have recently upgraded to Sonar 5.3 from 4.4.1 and seen duplicate key issue with one of our projects. I checked the collation and found database server and database to be case insensitive and column to be case sensitive. Should we change collation on the database to "Latin1_General_CS_AS" ? Changing the collation on the server is bit difficult but we can try with database. SELECT SERVERPROPERTY('COLLATION') Output: Latin1_General_CI_AS SELECT DATABASEPROPERTYEX('<SonarDatabaseName>',

sonarqube: why are background tasks only viewable by admins?

二次信任 提交于 2019-12-25 07:09:27
问题 We are testing an upgrade to Sonarqube5.3 and are having some of the issues identified in other StackOverflow posts, such as the Cobertura interactions. The problem I have is that I am not an administrator for the test server, so I can't look at the background tasks to find out why they are failing. Is there a way that the background task results can be printed in the sonar analysis logs? And is there a way to get the analysis in the build not to generate an exception when the background task

Issues (auto) closed and re-open

天大地大妈咪最大 提交于 2019-12-21 21:08:36
问题 Dear SonarQube Development team and other experts, I use SonarQube 5.3 and MSBuild Runner. A few weeks ago, I experienced issues when closing the program. These issues persisted even when leaving a file unchanged. Furthermore, these issues may be oustide the range of 1000 lines. I'm working on improving myself thanks especially to SonarQube. Currently, I eagerly await the next release, because: The next release has promised to fix among other things, the 1000 line restriction. My hope is that

IllegalStateException when migrating databases from SonarQube 5.3 to 5.6.2 (and 5.5)

萝らか妹 提交于 2019-12-12 03:35:20
问题 While trying to upgrade databases from SonarQube 5.3 to SonarQube 5.6.2, I am getting a "java.lang.IllegalStateException" with the message "Fail to decompress and deserialize source data" (originally caused by com.google.protobuf.InvalidProtocolBufferException: Stream is corrupted). I have tried this with several different databases (we have something like 40 teams using SonarQube 5.3 and wanting to upgrade) and with both 5.5 (in case a smaller step would have worked) and 5.6.2. I get the

SonarQube service not starting

て烟熏妆下的殇ゞ 提交于 2019-12-12 03:25:20
问题 We are seeing below error while starting SonarQube service. Looks like there is a duplicate entry while registering Quality Profile but I am not sure on the table. Since the service is not started, we cannot verify it from web. Can someone please advise. The issue occurred post creation of a new DB and copy of tables data from old DB. We are performing this to check new collation which is required for Sonar. 2016.04.26 15:41:53 INFO web[o.s.s.s.RegisterDebtModel] Register technical debt model

Unable to start SonarQube server after upgrade to SonarQube 5.4

寵の児 提交于 2019-12-11 10:43:40
问题 I am running a SonarQube server v5.3 natively on a Virtualbox running Ubuntu 15.10. To upgrade to v5.4 I shut down the SonarQube server and updated the packages from the ubuntu update center. I received no errors in the terminal during the upgrade, however once I attempted to view the server using the web interface I saw an errors message saying that the server encountered an error and to contact support. In the sonar/logs/sonar.log -file I found the following error output: 2016.03.14 11:59

Code coverage differences in sonarqube .Net

安稳与你 提交于 2019-12-11 09:53:55
问题 I found a scenario with SonarQube 5.3 where different values are being reported in code coverage from Visual Studio code coverage analysis. Here is a small reproduction, using the MSTest framework. I'm not able to determine if there is something wrong in what we are doing or if one of the applications is wrong. The object being tested [Serializable] public class Document : IEquatable<Document> { public long Id { get; set; } public string Name { get; set; } public long DocumentHandle { get;

SonarQube 5.3: IllegalArgumentException: There's no changeset on line 1352

吃可爱长大的小学妹 提交于 2019-12-10 16:21:49
问题 I try to migrate from 5.1 to 5.3 version of SonarQube. SonarQube plugins: Cobertura 1.6.3 (cobertura) C# 4.4 (csharp) Java 3.9 (java) XML 1.4 (xml) Git 1.0 (scmgit) SVN 1.2 (scmsvn) JavaScript 2.10 (javascript) My project use Java, XML, JavaScript and jaCoCo code coverage. The client side analysis works fine, but I have a stack-trace in logs during the server-side integration: (end of logs) 2016.02.04 10:45:17 INFO [o.s.s.c.s.ComputationStepExecutor] Log scanner context | time=11ms 2016.02.04

New code coverage metrics not returning values from SonarQube 5.3 API

怎甘沉沦 提交于 2019-12-08 13:14:46
问题 I need to fetch unit test coverage data for new code changes via the api. The metrics. I can see the data in SonarQubeDashboard but the api is not returning any values for the metrics like: new_coverage new_line_coverage (etc) I am invoking the api : https:///api/resources?format=json&metrics=ncloc,line_coverage,new_line_coverage Even the Public Nemo Instance does not return these metric values: https://nemo.sonarqube.org/api/resources?format=json&metrics=ncloc,line_coverage,new_line_coverage

Frozen “Still Working…” message when traversing rules in quality profile AND nameless rulesets in some rules

这一生的挚爱 提交于 2019-12-06 12:58:35
问题 I have a new instance of SQ 5.3. I imported couple of Java quality profiles from another SQ 5.3 instance (migrated from SQ 5.1.2). Then, when I open any Java quality profile I can see all rules belonging to it. But when I click at a rule to see its definition then I see the message "Still Working..." which doesn't disappear at all, even after a long time! What's more interesting: when I click at the 'scroll' button to get to the definition of the next rule then, for some rules, the definition