-
Suggestion
-
Resolution: Won't Do
-
None
-
None
-
0
-
We have a set of .NET code that relies on projects being siblings in a directory structure in order for dependencies to operate properly. Example:
- project1/MyAssembly
- project2/MyOtherAssembly
These projects would ideally build separately since they are being managed in different SCM repositories and have different life cycles. Since Bamboo does not support specifying an absolute path for the build workspace (both Jenkins and TeamCity do), the only option (without modifying the source/build scripts) is to bundle the jobs for these different assemblies into the same project/stage. This is not optimal.
Bamboo should allow for the workspace path to be specified as an absolute path to enable situations like this.