Community
Participate
Working Groups
I noticed the GMF-Tooling sonar job is still on the Hudson Sandbox [1]. Per bug 414773 we are planning on shutting down the sandbox end of March so we will need to migrate it to the GMF-Tooling HIPP if it is still necessary. Can we migrate this job over to the GMF-Tooling HIPP instance? Webmaster can help with copying over the job. [1] https://hudson.eclipse.org/sandbox/job/GMF-Tooling-Sonar
Adding Mickael since he's the sandbox job owner.
To my understanding, it requires some plugins to be installed and we missed to request installing them at the migration to HIPP. Can you please install it and move the job?
I migrated the job and disabled the sandbox one. https://hudson.eclipse.org/gmf-tooling/job/GMF-Tooling-Sonar/
I have just tried to revive this job at the HIPP. I see the problem with permissions as follows: (at the end of https://hudson.eclipse.org/gmf-tooling/job/GMF-Tooling-Sonar/32/console) Can you please grant the necessary permission or advice how to fix that? [workspace] $ mvn -f /home/hudson/genie.modeling.gmp.gmf-tooling/.hudson/jobs/GMF-Tooling-Sonar/workspace/pom.xml -e -B sonar:sonar -Dmaven.repo.local=/home/hudson/genie.modeling.gmp.gmf-tooling/.hudson/jobs/GMF-Tooling-Sonar/workspace/.maven/repo -Dsonar.jdbc.driver=org.postgresql.Driver -Dsonar.jdbc.url=jdbc:postgresql://sonar/sonar ******** ******** -Dsonar.host.url=https://dev.eclipse.org/sonar FATAL: command execution failed java.io.IOException: Cannot run program "mvn" (in directory "/home/hudson/genie.modeling.gmp.gmf-tooling/.hudson/jobs/GMF-Tooling-Sonar/workspace"): error=13, Permission denied at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041) at hudson.Proc$LocalProc.<init>(Proc.java:187) at hudson.Proc$LocalProc.<init>(Proc.java:157) at hudson.Launcher$LocalLauncher.launch(Launcher.java:649) at hudson.Launcher$ProcStarter.start(Launcher.java:266) at hudson.Launcher$ProcStarter.join(Launcher.java:273) at hudson.tasks.Maven.perform(Maven.java:255) at hudson.plugins.sonar.utils.SonarMaven.executeMaven(SonarMaven.java:149) at hudson.plugins.sonar.SonarPublisher.executeSonar(SonarPublisher.java:331) at hudson.plugins.sonar.SonarPublisher.perform(SonarPublisher.java:292) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:51) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:646) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:624) at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:600) at hudson.model.Build$RunnerImpl.post2(Build.java:163) at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:566) at hudson.model.Run.run(Run.java:1414) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:40) at hudson.model.ResourceController.execute(ResourceController.java:82) at hudson.model.Executor.run(Executor.java:137) Caused by: java.io.IOException: error=13, Permission denied at java.lang.UNIXProcess.forkAndExec(Native Method) at java.lang.UNIXProcess.<init>(UNIXProcess.java:135) at java.lang.ProcessImpl.start(ProcessImpl.java:130) at java.lang.ProcessBuilder.start(ProcessBuilder.java:1022) ... 19 more Sonar analysis completed: FAILURE Sending e-mails to: mistria@redhat.com hillairet@montages.com Finished: FAILURE
IIRC, this happens because the Sonar plugin relies on the "Legacy" Maven 2 plugin, which is probably missing on GMF-Tooling HIPP.
(In reply to Mickael Istria from comment #5) > IIRC, this happens because the Sonar plugin relies on the "Legacy" Maven 2 > plugin, which is probably missing on GMF-Tooling HIPP. Sorry I had forgot about this. The Legacy configuration is setup in the newer HIPP images but GMF-Tooling was deployed previous to that so it did not have this config. I have setup the Maven 2 Legacy plugin now. Can you try again?
Nope, the same problem: https://hudson.eclipse.org/gmf-tooling/job/GMF-Tooling-Sonar/33/console
(In reply to Michael Golubev from comment #7) > Nope, the same problem: > https://hudson.eclipse.org/gmf-tooling/job/GMF-Tooling-Sonar/33/console I hope you don't mind but I started a new job. There was a setting for Sonar in the job under "Advanced" that said to inherit the Maven version from job. I decided to see if explicitly setting it to maven-3.0.5 will help.
Thanks, it works now.
