Setting up Jenkins and Sonar

Migrating Jenkins to a new host server:

Tasks:

1. Install Jenkins application on the new host.
   1. Download jenkins.war from http://jenkins-ci.org/.
   2. Deploy the war to a servlet container such as tomcat.
2. Configuration and Data Migration.
1. Copy the jenkins home directory from the old host.
2. Set JENKINS_HOME environment variable to point to this directory.
3. Start Jenkins.
4. Verify that jenkins web interface displays all the jobs and reports correctly.
5. Update DNS records to the point to the new host (This should cause github hook to point to the new host).
6. Verify correct working.
   
   1. Verify deploying to nexus repo.
   2. Verify deploying to Fedora 4 demo server.
   3. Verify IRC notification.
   4. Verify sonar plugin configuration.

Migrating Sonar to a new host:

Tasks:

1. Install Sonar on the new host.
   1. Download sonarqube.zip from http://www.sonarqube.org/downloads/ and extract it.
2. Database migration.
   1. Create a database dump of the sonar database from the old host.
   2. Import the database to the new host's sql server.
3. Configure sonar.properties, wrapper.properties, and logback.xml under conf/ directory in reference to the old host's configuration.
   1. Use the current database name, user, and password in place of the old configuration.
4. Copy extensions/plugins from old host.
   1. Download newer version of the plugins, if they are not compatible with the new host's sonar version. See plugins version matrix.
5. Start the sonar server.
6. Goto <SONAR_BASE_URL>/setup to complete database migration.
7. Verify that sonar web interface display all past reports.
8. Update DNS to point to new host.
9. Verify integration with Jenkins server.

Note: Please read the release notes and upgrade steps, if you are upgrading Jenkins / Sonar as a part of the migration.