-
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.
[BAM-10187] Allow specification of absolute paths for the build workspace
John Farrier
added a comment - Not allowing absolute paths creates problems for our automated testing which requires a large database of information. Configuration of this database on a normal development machine is drastically different than on our Bamboo server since each build configuration we have would require its own local database copy. This database copy would then require an unreasonable amount of data duplication and storage. While we have workarounds in place, it is making continuous integration for our project more challenging than need be.
John Farrier
added a comment - Not allowing absolute paths creates problems for our automated testing which requires a large database of information. Configuration of this database on a normal development machine is drastically different than on our Bamboo server since each build configuration we have would require its own local database copy. This database copy would then require an unreasonable amount of data duplication and storage. While we have workarounds in place, it is making continuous integration for our project more challenging than need be. 
Samuel Cameron
added a comment - I have a different situation where an absolute working directory is needed.
After being built, a hash of each file is created. The hash value is different when the working directory is different. This hash is required by our third party testing.
Samuel Cameron
added a comment - I have a different situation where an absolute working directory is needed.
After being built, a hash of each file is created. The hash value is different when the working directory is different. This hash is required by our third party testing. 
Hi everyone,
Thank you for your interest in this issue.
While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future.
We believe that this problem can be solved either by using Artifacts or by mapping external directories into agent's workspace.
Kind regards,
Bamboo Team