-
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
Workflow | Original: JAC Suggestion Workflow [ 3014080 ] | New: JAC Suggestion Workflow 3 [ 3606425 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Won't Do [ 10000 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Resolved [ 5 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2702011 ] | New: JAC Suggestion Workflow [ 3014080 ] |
UIS | New: 0 |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1420186 ] | New: Confluence Workflow - Public Facing v4 [ 2702011 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Component/s | New: Builds [ 11222 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 610137 ] | New: Bamboo Workflow 2016 v1 [ 1420186 ] |
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