At first I had SonarQube installed together with Jenkins on the same server. SonarQube is quite resource demanding and it was causing slowness of the other jobs / tasks running on Jenkins.
Moving to other instance was simple as installing SonarQube on other server and configuring Jenkins to use new SonarQube instance.
Steps required
Moving to other instance was simple as installing SonarQube on other server and configuring Jenkins to use new SonarQube instance.
Steps required
- Java runtime environment
- SonarQube binaries
- MSSQL JDBC driver (make sure you get sqljdbc_auth.dll available on PATH)
- SonarQube configuration was copied from old server to new (sonarqube/conf/*)
- SonarQube instance was registered as service and started.
- Once the service is running then try to access it in browser, if it is not accessible then check logs (sonarqube/logs) and resolve.
- Once the web is up and running there had to be installed language plugins again.
- Jenkins configuration have to be updated with new SonarQube url (Manage Jenkins > Configure System)
No comments:
Post a Comment