sonarqube5.6

sonarqube 5.6 & LDAP 2.0 failing to authenticate

試著忘記壹切 提交于 2020-01-21 05:11:26
问题 I am testing an upgrade to sonarqube 5.6 and have installed the ldap 2.0 plugin & copied the relevant configuration forward to my test 5.6 setup. The relevant config is sonar.security.realm=LDAP ldap.url=ldaps://xxxx:636 ldap.bindDn=uid=xxxx,ou=xxxx,dc=xxxx,dc=xxxx ldap.bindPassword=xxxx ldap.user.baseDn=dc=xxxx,dc=com ldap.user.request=(&(objectClass=person)(mail={login})) ldap.user.realNameAttribute=cn ldap.user.emailAttribute=mail I have the following set in conf/sonar.properties sonar.log

SonarQube 5.6 FileNotFound exception during AST Scan

天涯浪子 提交于 2019-12-25 08:07:12
问题 During the AST Scan, I get a FileNotFoundException looking for a symbols-34.pb file: ERROR: Error during SonarQube Scanner execution org.sonar.squidbridge.api.AnalysisException: SonarQube is unable to analyze file : '/workingDir/src/main/java/package/JavaFile.java' at org.sonar.java.ast.JavaAstScanner.simpleScan(JavaAstScanner.java:93) at org.sonar.java.ast.JavaAstScanner.scan(JavaAstScanner.java:67) at org.sonar.java.JavaSquid.scanSources(JavaSquid.java:133) at org.sonar.java.JavaSquid.scan

Sonarqube 5.6.3 reopens issue marked as won't fix

浪尽此生 提交于 2019-12-24 10:16:09
问题 we are using SonarQube version 5.6.3 and it is installed on linux server( CentOS release 6.8 ). Even after marking issue as "Won't Fix" manually, the issue seems to get open after another analysis in jenkins ( Jenkins ver. 1.642.3 ) . Out of many engagements (appprox. 100+), One engagement holds its project snapshot from August 2015 to till date. I was thinking of deleting the snapshot, but engagement wants an another alternative. I am not sure what is causing this issue. Does anyone has the

Elasticsearch bulk index error on Sonar startup

若如初见. 提交于 2019-12-22 06:04:40
问题 Would someone be able to assist on the error below? It is occurring on the start up of SonarQube 5.6 running on Java 8u71 and an Oracle database. This instance was just update from 5.2. I had the Puppet addon and uninstalled it as an attempt to solve the error. I confirm Elasticsearch is on port 9001 after startup. 2016.06.13 00:16:04 ERROR web[o.s.s.es.BulkIndexer] Fail to execute bulk index request: Bulk[671 index request(s) on index rules and type activeRule] org.elasticsearch.transport

Elasticsearch bulk index error on Sonar startup

浪子不回头ぞ 提交于 2019-12-22 06:03:11
问题 Would someone be able to assist on the error below? It is occurring on the start up of SonarQube 5.6 running on Java 8u71 and an Oracle database. This instance was just update from 5.2. I had the Puppet addon and uninstalled it as an attempt to solve the error. I confirm Elasticsearch is on port 9001 after startup. 2016.06.13 00:16:04 ERROR web[o.s.s.es.BulkIndexer] Fail to execute bulk index request: Bulk[671 index request(s) on index rules and type activeRule] org.elasticsearch.transport

SonarQube default credentials for internal H2 db?

六眼飞鱼酱① 提交于 2019-12-13 14:12:26
问题 I'm running SonarQube 5.6.1 and am trying to save a view that I created. To do that, I want to take a peek at H2 DB that Sonar (according to it's own readme) uses for internal embedded DB. I've ran the H2 jar file and in console was able to log in to dummy DB. If SonarQUbe is running, I can't connect. So, what are default credentials for that DB? Tried my user credentials and admin/admin, none work. Admin/admin is default for SonarQube administrator user. 回答1: The default values are sonar

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

BuildBreaker Does not fails in issues and preview mode but fails in publish mode - SonarQube5.6.1

那年仲夏 提交于 2019-12-12 03:03:53
问题 I am using Buildbreaker2.4 plugin in sonarQube5.6.1. When i run the below command, mvn sonar:sonar -Dsonar.issuesReport.html.enable=true -Dsonar.analysis.mode=publish Buildbreaker fails with critical issues But when i run any of the below two commands, it gets passed. mvn sonar:sonar -Dsonar.issuesReport.html.enable=true -Dsonar.analysis.mode=issues mvn sonar:sonar -Dsonar.issuesReport.html.enable=true -Dsonar.analysis.mode=preview Suggest me on what might be the problem. 回答1: for fail in

SonarQube won't display System Info

*爱你&永不变心* 提交于 2019-12-12 00:52:13
问题 When I try to display the system info for my SonarQube 5.6 server I get an exception in the logs on the page. Any idea what could be causing this? This question (Getting an error as "Could not initialize class sun.net.www.protocol.http.HttpURLConnection" in ZK Framework) implies that the jar is missing from the jdk. Is that possible? I'm using java-1.8.0-openjdk-1.8.0.151-1.b12.el6_9.x86_64. Has the HttpUrlConnection implementation been changed? 2018.04.23 12:12:15 ERROR web[rails] Java:

Elasticsearch bulk index error on Sonar startup

只愿长相守 提交于 2019-12-05 10:35:43
Would someone be able to assist on the error below? It is occurring on the start up of SonarQube 5.6 running on Java 8u71 and an Oracle database. This instance was just update from 5.2. I had the Puppet addon and uninstalled it as an attempt to solve the error. I confirm Elasticsearch is on port 9001 after startup. 2016.06.13 00:16:04 ERROR web[o.s.s.es.BulkIndexer] Fail to execute bulk index request: Bulk[671 index request(s) on index rules and type activeRule] org.elasticsearch.transport.RemoteTransportException: [sonar-1465791343547][inet[/127.0.0.1:9001]][indices:data/write/bulk] Caused by