amirkibbar
created JENKINS-15463
JaCoCo Jenkins plugin does not work on a linux slave
Issue Type:
Bug
Affects Versions:
current
Assignee:
Ognjen Bubalo
Components:
jacoco
Created:
10/Oct/12 1:10 PM
Description:
i'm using jacoco to produce coverage reports with jacoco-maven-plugin. The configuration is the basic simple one - just like in jacoco's example. The build has a post build action that collects the jacoco report - this is from the jacoco jenkins plugin.
When running the build on a linux slave the following error appears in the log:
10:54:20 java.lang.IllegalStateException: basedir \usr\local\jenkins\workspace\carmel-commons does not exist.
10:54:20 at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:879)
10:54:20 at hudson.plugins.jacoco.JacocoPublisher.resolveDirPaths(JacocoPublisher.java:116)
10:54:20 at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:181)
10:54:20 at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
10:54:20 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:717)
10:54:20 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:692)
10:54:20 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:994)
10:54:20 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:639)
10:54:20 at hudson.model.Run.execute(Run.java:1527)
10:54:20 at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
10:54:20 at hudson.model.ResourceController.execute(ResourceController.java:88)
10:54:20 at hudson.model.Executor.run(Executor.java:236)
you can see that the plugin attempts to access \usr\local\jenkins\workspace\carmel-commons as the base dir - the slashes it uses are windows slashes and not linux ones.
Environment:
master jenkins on windows, slave on linux
Project:
Jenkins
Labels:
windows
linux
jacoco
slave
Priority:
Major
Reporter:
amirkibbar
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira