{"id":771,"date":"2013-12-08T09:40:59","date_gmt":"2013-12-08T08:40:59","guid":{"rendered":"http:\/\/qualilogy.com\/en\/?p=771"},"modified":"2013-12-08T16:25:54","modified_gmt":"2013-12-08T15:25:54","slug":"upgrade-sonarqube-runner-jenkins","status":"publish","type":"post","link":"http:\/\/qualilogy.com\/en\/upgrade-sonarqube-runner-jenkins\/","title":{"rendered":"Upgrade SonarQube-Runner and Jenkins"},"content":{"rendered":"

\"JenkinsUpgrade\"<\/a>I updated my version of SonarQube int the post SonarQube Upgrade 4.0<\/a>,\u00a0which was an opportunity to document some errors encountered.<\/p>\n

I also wanted to updater other components such as the SonarQube-Runner and Jenkins and Mr. Jenkins caused me some problems.<\/p>\n

So this post will allow us to see an upgrade of the SonarQube-Runner and Jenkins, as well as solve (or avoid) the errors encountered. <\/p>\n

Jenkins Upgrade<\/h2>\n

After completing the upgrade of SonarQube in 4.0, I went into the portal Jenkins to run an analysis. I noticed at that time that there was a new version of Jenkins, so I decided to take the opportunity to also update it.<\/p>\n

But this time, instead of installing Jenkins as a Windows service<\/a>, as we have seen there a few times ago, I thought it would be an opportunity to install Jenkins with a Windows install, I mean, from an installation executable.<\/p>\n

So I went on the Jenkins site<\/a> in order to download the Windos native \"DownloadJenkinsWindows\"<\/a>package, a zipped file ‘jenkins-1.541.zip’.<\/p>\n

\"InstallJenkinsSetup\"<\/a>After we unziip it, we now have a ‘setup.exe’ file and a ‘jenkins-1.541.msi’ install file.<\/p>\n

I will check that the current Jenkins service is stopped. And I will launch the ‘setup.exe’. The install – in fact the update of the Windows service Jenkins – goes trough different steps: ‘Installing’, ‘Validating install’, ‘Starting service’, … I’ll spare you the details.<\/p>\n

I know that the service has been updated for the good reason that … it does not start. Well, I got the same error that we met during our first install of Jenkins as a Windows service<\/a>, which is that I need to change the Windows user in order to start the service correctly.<\/p>\n

Once done , the Jenkins service starts without a problem, but against impossible to display the portal Jenkins at its usual url http:\/\/localhost:8080\/<\/strong>. I see a strong activity of my computer from the Windows Task List, a Java process that takes a lot of CPU, continuously.<\/p>\n

I waited patiently, I stopped \/ started Jenkins\u00a0several times, and even rebooted my computer, but nothing happens. In fact, navigating through the various Jenkins logs, I discovered that a library was missing (a .jar file) so there was no possible way to get a correct functioning of the Jenkins webapp. Although the Se\u00f1or Jenkins tried to launch continuously in an unsuccessful loop and without any message of explanation of what it was doing.<\/p>\n

So I ended up uninstalling the Jenkins application using the same procedure as in the post about installing Jenkins as a Windows service<\/a>, from a war file. Thus, I will not detail again this installation, but simply list the main steps:<\/p>\n

    \n
  1. Download the ‘jenkins.war’ file from the Jenkins site.<\/a><\/li>\n
  2. Launch Jenkins from a DOS windows with the command java -jar jenkins.war<\/strong>.<\/li>\n
  3. In the Jenkins portal that opens at the url http:\/\/localhost:8080\/<\/strong>, goes to the menu ‘Manage Jenkins’, then ‘Install as Windows service’.<\/li>\n
  4. Follow the procedure of installation and once Jenkins is installed (or updated) as a Windows service, I have to modify the Windows user by default, with one with enough rights to start Jenkins. This step is probably specific to my laptop, it should be optional for a server installation of Jenkins.<\/li>\n
  5. Then I change the configuration of Jenkins in the file \u2018jenkins.xml<\/strong>\u2018) to make it point to my current repository, and recover all existing analysis jobs.<\/li>\n<\/ol>\n

    And then, finally, I can start Jenkins.<\/p>\n

    SonarQube is missing<\/h2>\n

    Well, maybe I can start Jenkins but no SonarQube analysis job is running. I launch it and nothing happens.Not even an error message. I go to check the installed plugins and the SonarQube plugin is present in my current configuration. However, when I go to the configuration page of Jenkins (menu ‘Manage Jenkins’), the part corresponding to the settings of SonarQube<\/a> is not there.<\/p>\n

    I spent a lot of time and it took me several failed attempts (including a re-install of the plugin SonarQube which resulted in the loss of the configurations of my analysis) before discovering the error. I do not know how it could happen, if it comes from the unsuccessful installation of Jenkins with a native Windows package, or simply a bad manipulation on my part, but the plugin ‘Maven Integration’ was disabled and this is what did cause that SonarQube became invisible. As I am not a Maveniste, it may well be that I disactivated this plugin without remembering it.<\/p>\n

    \"JenkinsMavenIntegrationPlugin\"<\/a><\/p>\n

    I did reactivate it and my SonarQube configuration did come back at it was originally. (see the posts about installing SonarQube as a Windows service<\/a>, and installing the SonarQube plugins for Jenkins<\/a>).<\/p>\n

    SonarQube-Runner upgrade<\/h2>\n

    The update SonarQube Runner has not been a problem. So again, I will resume the main steps (as seen in the post about the\u00a0installation of SonarQube-Runner<\/a>):<\/p>\n

      \n
    1. Download the SonarQube Runner installation file from the page Installing and Configuring SonarQube Runner<\/a>, in the 2.3 version in my case (at the date of this post).<\/li>\n
    2. Unzip this file into a directory \u2018sonar-runner-2.3\u2019.<\/li>\n
    3. Modify the configuration file ‘sonar-runner.properties’ in order to indicate the localisation of SonarQube and of our Oracle database.<\/li>\n<\/ol>\n

      \"\"<\/a><\/p>\n

      \"JenkinsSonarRunnerInstallation\"<\/a>In Jenkins, we go back to the configuration page (menu ‘Manage Jenkins’) and opten the section dedicated to the SonarQube-Runner configuration. Just specify the location of this new version and that’s it.<\/p>\n

      \"JenkinsSonarRunnerInstallation2\"<\/a><\/p>\n

      Et voil\u00e0 ! I can resume my analysis, all with a full up-to-date environment with SonarQube the SonarQube Runner and Jenkins.<\/p>\n

      Last tip: if you lost the configuration of a job analysis in Jenkins, you can retrieve it from a backup of your repository.<\/p>\n

      \"JenkinsJobConfigXML\"<\/a>The analysis<\/span> are located<\/span> in the ‘<\/span>Jobs’ folder<\/span>,<\/span> with<\/span> a subdirectory<\/span> for each analysis.<\/span> Where you will find<\/span> a <\/span><\/span>config.xml<\/strong> file with the configuration of the job, as for example the different SonarQube properties I indicate as parameters of the analysis.<\/p>\n

      Conclusion<\/h2>\n

      I must say that<\/span> I did not try<\/span> to<\/span> investigate furthermore the origin of the errors I have encountered?<\/span>.<\/span> But<\/span> in conclusion, we<\/span> can say that:<\/span><\/span><\/p>\n

      Installing the<\/span> Windows<\/span> Jenkins<\/span> service from<\/span> a file<\/span>. War<\/span> seems more<\/span> stable, although<\/span> less<\/span> natural<\/span> than from a<\/span> setup executable<\/span> (setup.exe<\/span> deviation).<\/span>
      \nIf the<\/span> configuration<\/span> SonarQube<\/span> disappeared from<\/span> Jenkins<\/span> configuration page<\/span>, verify<\/span> that you have<\/span> the<\/span> plugin ‘<\/span>Maven<\/span> Integration<\/span>‘<\/span> installed.<\/span> Do not<\/span> ask me why,<\/span> I do not use<\/span> Maven<\/span>.<\/span><\/p>\n

        \n
      • Installing Jenkins as a Windows service from a .war file seems more stable, although less natural than from a setup file.<\/li>\n
      • If the SonarQube configuration disappeared from the Jenkins configuration page, verify that you have the plugin ‘Maven Integration’ installed. Do not ask me why, I do not use Maven.<\/li>\n<\/ul>\n

        Too bad<\/span> that no error<\/span> message<\/span> tells us<\/span> that it is not<\/span> possible to perform<\/span> an analysis,<\/span> as<\/span> Jenkins<\/span> does not know<\/span> how to locate<\/span> SonarQube<\/span>.<\/span> But at least<\/span> now, if<\/span> this error occurs,<\/span> we know<\/span> how to correct it<\/span>. <\/span><\/span><\/p>\n

        And finally, we<\/span> have also seen<\/span> how to retrieve the<\/span> Jenkins<\/span> configuration<\/span> of our<\/span> analysis<\/span> jobs<\/span>.<\/span> And<\/span> our<\/span> environment is completely<\/span> up-to-tade<\/span>.<\/span> Well, that was worth<\/span> a<\/span> post<\/span>!<\/span><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

        I updated my version of SonarQube int the post SonarQube Upgrade 4.0,\u00a0which was an opportunity to document some errors encountered. I also wanted to updater other components such as the SonarQube-Runner and Jenkins and Mr. Jenkins caused me some problems. So this post will allow us to see an upgrade of the SonarQube-Runner and Jenkins, […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-771","post","type-post","status-publish","format-standard","hentry","category-sonar-installation"],"_links":{"self":[{"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/posts\/771"}],"collection":[{"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/comments?post=771"}],"version-history":[{"count":12,"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/posts\/771\/revisions"}],"predecessor-version":[{"id":774,"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/posts\/771\/revisions\/774"}],"wp:attachment":[{"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/media?parent=771"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/categories?post=771"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/qualilogy.com\/en\/wp-json\/wp\/v2\/tags?post=771"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}