|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
I have investigated the problem: it is due to an incorrect check in FitnesseExecutor.getAbsolutePathToFileThatMayBeRelativeToWorkspace: if the user specifies a directory-name which coincidentally is also the name of a directory in the root directory of the whole filesystem, then it assumes the latter and ends up passing a null pointer to ProcStarter.cmds(). The following patch fixes the problem on *Nix-systems, though it will have to be adjusted to work properly on Windows:
diff --git a/src/main/java/hudson/plugins/fitnesse/FitnesseExecutor.java b/src/main/java/hudson/plugins/fitnesse/FitnesseExecutor.java
index 5a12e24..60908a3 100644
— a/src/main/java/hudson/plugins/fitnesse/FitnesseExecutor.java
+++ b/src/main/java/hudson/plugins/fitnesse/FitnesseExecutor.java
@@ -315,7 +315,7 @@ public class FitnesseExecutor {
}
static String getAbsolutePathToFileThatMayBeRelativeToWorkspace(FilePath workingDirectory, String fileName) { - if (new File(fileName).exists()) return fileName; + if (fileName.startsWith("/")) return fileName; return new File(workingDirectory.getRemote(), fileName).getAbsolutePath(); }
}