sonarqube-ops

问题 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

问题 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>',

问题 After sonarqube 6.6 upgrade from 6.5 (with Debian package), sonar is unable to start. I did not update plugins before upgrade. I just let the standard Debian package upgrade. I am using an external database (Postgresql). I found the following errors in web.log : 2017.10.24 18:12:34 ERROR web[][o.s.s.es.BulkIndexer] index [components], type [component], id [AVgpp1_-x6lKXwnU0BYQ], message [java.lang.IllegalArgumentException: can't specify parent if no parent field has been configured] 2017.10

问题 I've got an instance of sonarqube 5.5 running. I wanted to use the sonar-ldap-plugin 1.5.1 in order to delegate the authentication and authorization to the Active Directory service of my company. The configuration for the LDAP plugin is the following (modulo some obfuscation): sonar.authenticator.createUsers=false sonar.security.savePassword=false sonar.security.realm=LDAP ldap.url=ldap://host.my.domain ldap.user.baseDn=OU=Users,OU=Organic Units,DC=my,DC=domain ldap.user.request=(&

问题 We are trying to upgrade to lastest sonarqube 5.5. We have mariadb 10.1 (latest) and since now we had no problems with sonarqube. Now, with the upgrade, sonarqube will not boot. It says: Unsupported mysql version: 5.5. Minimal supported version is 5.6. Is there any trick we can use to make "sonar think" we are using mysql 5.6? 回答1: You could change the MINIMAL_SUPPORTED_DB_VERSIONS member in the Sonarqube's class https://github.com/SonarSource/sonarqube/blob/master/sonar-db/src/main/java/org

问题 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

问题 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

问题 We currently have a jenkins pipeline using Multibranch Workflow plugin . Each git branch execute a sonarqube analysis creating a sonarqube project using the sonar.branch property. This is very useful because each branch is being analyzed before merge it, the problem appear when a branch is merged with master and disappear on GIT, the project continues on sonarqube and need to be deleted manually. Is There a way to do it automatically? or any other recomendation? 回答1: You can define a method

问题 Trying to setup SonarQube on EC2 using what should be basic install settings. List item Setup a standard EC2 AWS LINUX Ami attached to M4 large SSH into EC2 instance Install JAVA Set to use JAVA8 wget https://sonarsource.bintray.com/Distribution/sonarqube/sonarqube-6.4.zip unzip into the /etc dir run sudo ./sonar.sh start Instance starts But when I try to go to the app it never comes up when I try either the IPv4 Public IP 187.187.87.87:9000 (ex not real IP) or try ec2-134-73-134-114.compute

问题 Sonarqube official docker image, is not persisting any configuration changes like: creating users, changing root password or even installing new plugins . Once the container is restarted, all the configuration changes disappear and the installed plugins are lost. Even the projects' keys and their previous QA analytics data is unavailable after a restart. How can we persist the data when using Sonarqube's official docker image? 回答1: Sonarqube image comes with a temporary h2 database engine