Build Definition with spaces in Working Dir path

It should be OK if the working dir has spaces. Does the command line also have spaces?

The problem I'm having is that the working dir has spaces.

I tried enclosing the path in quotes but that doesn't work.

Mike Brosnan

I tried making a "Command Line - Jazz Build Engine" Build Definition and I was able to run a successful build when specifying a working directory which contains spaces.

Ex:
Command: cmd /c dir
Working directory: c:\dir with spaces (with no quotes)


As Nick said, is it possible your command has spaces?

As an example, the following command would fail (even though I do have a directory called "dir with spaces").
Command: cmd /c dir c:\dir with spaces

To get this command to work in Windows you would have to do this:
Command: cmd /c dir "c:\dir with spaces"

Please provide additional information as to what your command is, and what are the errors you are receiving.

The problem I'm having is that the working dir has spaces.

I tried enclosing the path in quotes but that doesn't work.

Mike Brosnan

I tried making a "Command Line - Jazz Build Engine" Build Definition and I was able to run a successful build when specifying a working directory which contains spaces.

Ex:
Command: cmd /c dir
Working directory: c:\dir with spaces (with no quotes)


As Nick said, is it possible your command has spaces?

As an example, the following command would fail (even though I do have a directory called "dir with spaces").
Command: cmd /c dir c:\dir with spaces

To get this command to work in Windows you would have to do this:
Command: cmd /c dir "c:\dir with spaces"

Please provide additional information as to what your command is, and what are the errors you are receiving.


The directory I was specifying in the Working Directory was on the D: drive, and the build engine is set up on the default path on C:.

I'll try that again on the C: drive with quotes as you suggest,

We're on RTC 2.0.0.2.iFix4

thanks

Mike

I tested this again.

I'm just using cmd /c dir as the command.

I can add "C:\Documents and Settings" on the command line, or in the Arguments field in the build definition and that works fine

When I use "C:\Documents and Settings" in the Working Directory field, it fails with the following message

2010-12-10 06:28:41 running on host: EI0085VWIN
2010-12-10 06:28:41 Should build occur?
2010-12-10 06:28:41 Yes: Always build a user initiated request.
2010-12-10 06:28:42 Invoking pre-build participant "com.ibm.team.build.jazzscm"
Accepting changes into workspace "a449909 Toolkits DNC Stream Workspace" ...
Fetching files to fetch destination "C:\RTCBUILD\DNC\DNC\DNC" ...
2010-12-10 06:28:47 Invoking build participant "com.ibm.team.build.cmdline"
java.io.IOException: The filename, directory name, or volume label syntax is incorrect.
at java.io.Win32FileSystem.canonicalize(Win32FileSystem.java:434)
at java.io.File.getCanonicalPath(File.java:560)
at com.ibm.team.build.internal.engine.CommandLineBuildParticipant.getMissingWorkingDirException(CommandLineBuildParticipant.java:360)
at com.ibm.team.build.internal.engine.CommandLineBuildParticipant.getWorkingDirectory(CommandLineBuildParticipant.java:349)
at com.ibm.team.build.internal.engine.CommandLineBuildParticipant.validateWorkingDir(CommandLineBuildParticipant.java:125)
at com.ibm.team.build.internal.engine.CommandLineBuildParticipant.validateProperties(CommandLineBuildParticipant.java:106)
at com.ibm.team.build.internal.engine.CommandLineBuildParticipant.build(CommandLineBuildParticipant.java:71)
at com.ibm.team.build.internal.engine.BuildLoop.invokeBuildParticipants(BuildLoop.java:655)
at com.ibm.team.build.internal.engine.BuildLoop$2.run(BuildLoop.java:468)
at java.lang.Thread.run(Thread.java:811)

One other thing to check: which JDK/JRE are you using to run JBE (i.e. what do you get if you run 'java -version' from the dir where you normally start JBE)?
Try running with the JDK included in the Eclipse client. For details, see:
https://jazz.net/wiki/bin/view/Main/BuildFAQ#WhichJDK

I set up the JBE to run as a service and I'm using the JDK included with RTC

C:\jazz\service>C:\jazz\client\eclipse\jdk\bin\java -version
java version "1.5.0"
Java(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20091106a (SR11
))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows Server 2003 x86-32 j9vmwi322
3-20091104 (JIT enabled)
J9VM - 20091103_45935_lHdSMr
JIT - 20091016_1845_r8
GC - 20091026_AA)
JCL - 20091106

C:\jazz\service>

I set up the JBE to run as a service and I'm using the JDK included with RTC

I'm going to test with JBE as a service as well (and try to do exactly what you did). In the meantime, can you try running JBE normally (not in a service) and try again?