-
Bug
-
Resolution: Low Engagement
-
Medium
-
None
-
2.2.1
-
1
-
Severity 2 - Major
-
if there is a win registry entry
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor and its AutoRun property is to execute cd \
then the builder (ant) will be started in c:\ or d:\ instead of in the correct working copy directory path - and the builder will not find the files it is looking for.
Bamboo should make sure that the builder/build script is executed in the right directory. ATM bamboo assumes that there are not default commands run when a command shell is opened.
This directory is known to bamboo - for example
Starting to build 'TESTCI - TESTCIPLAN'
... running command line: D:\devtools\apache-ant-1.7.1\bin\ant.bat -f build.xml -debug build
... in : D:\Bamboo\bamboo-home\xml-data\build-dir\TESTCI-TESTCIKEY\build
... using java.home: D:\devtools\Java\jdk1.5.0_17
A good place to read about the registry setting for the command shell : http://www.msfn.org/board/lofiversion/index.php/t45360.html
[BAM-3858] Bamboo starts builder in wrong directory in command shell in windows if HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor is set
Resolution | New: Low Engagement [ 10300 ] | |
Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
Labels | New: cleanup-seos-fy25 |
Support reference count | New: 1 |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Workflow | Original: Bamboo Workflow 2016 v1 - Restricted [ 1441196 ] | New: JAC Bug Workflow v3 [ 3380938 ] |
Status | Original: Open [ 1 ] | New: Needs Triage [ 10030 ] |
Symptom Severity | Original: Major [ 14431 ] | New: Severity 2 - Major [ 15831 ] |
Symptom Severity | New: Major [ 14431 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1416841 ] | New: Bamboo Workflow 2016 v1 - Restricted [ 1441196 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 618883 ] | New: Bamboo Workflow 2016 v1 [ 1416841 ] |
Workflow | Original: Bamboo Workflow 2014 [ 605087 ] | New: Bamboo Workflow 2014 v2 [ 618883 ] |