- changed status to open
Support spaces in script path
The plug-in fails to run the script file when you install Bamboo in a path with a space (like \Program Files), probably due to the path not being escaped when generating the temporary .cmd file wrapper:
28-Feb-2014 19:50:14 Starting task 'Copy Files' of type 'com.stellarity.bamboo.powershell-task:powerShellTask'
28-Feb-2014 19:50:14 Unable to find executable at C:\Program. Will try to run it anyway.
28-Feb-2014 19:50:14
Beginning to execute external process for build 'XYZ'
... running command line:
C:\Program Files\Bamboo\temp\XYZ-PowerShellTask-2027515183542512523.cmd
... in: C:\bamboo-home\xml-data\build-dir\XYZ\build
28-Feb-2014 19:50:16 . : The term 'C:\Program' is not recognized as the name of a cmdlet, function,
28-Feb-2014 19:50:16 script file, or operable program. Check the spelling of the name, or if a path
28-Feb-2014 19:50:16 was included, verify that the path is correct and try again.
28-Feb-2014 19:50:16 At line:1 char:30
28-Feb-2014 19:50:16 + &{$ErrorActionPreference=1;. C:\Program
28-Feb-2014 19:50:16 Files\Bamboo\temp\XYZ ...
28-Feb-2014 19:50:16 + ~~
28-Feb-2014 19:50:16 + CategoryInfo : ObjectNotFound: (C:\Program:String) [], ParentCo
28-Feb-2014 19:50:16 ntainsErrorRecordException
28-Feb-2014 19:50:16 + FullyQualifiedErrorId : CommandNotFoundException
28-Feb-2014 19:50:16
28-Feb-2014 19:50:16 Failing task since return code of [C:\Program Files\Bamboo\temp\XYZ-PowerShellTask-2027515183542512523.cmd] was 1 while expected 0
28-Feb-2014 19:50:16 Finished task 'Copy Files'
I was able to get around the issue by moving Bamboo to C:\Bamboo\ but that's not ideal.
Comments (2)
-
-
- changed status to resolved
Fixed in 1.1.5 and 1.0.8.
- Log in to comment