-
Suggestion
-
Resolution: Won't Do
-
None
-
None
-
0
-
From BSP-749
Imagine I have two projects or plans:
ProjA-Build
ProjA-TestThe two (in the case of devenv and NUnit) may even be using different builders, meaning that it's impossible or undesirable (due to timing) to have the testing project actually build things themselves.
What is the preferred approach to doing this without forcing a separate p4 sync and build? Ideally, what I'd like is to have the ProjA-Test base itself completely on the directory and data from ProjA-Build. Is that possible? Would I have to have artifacts and load the artifacts or something? (this would be potentially difficult with NUnit, which requires the DLLs coming from devenv.com)
- is duplicated by
-
BAM-2839 Allow sharing of local working directory between plans.
- Closed
- is related to
-
BAM-10187 Allow specification of absolute paths for the build workspace
- Closed
-
BAM-10051 Allow Perforce to continue using the Workspace as Working Directory when the Checkout Task is removed
- Closed
- relates to
-
BAM-11984 Cross-plan build artifacts or built-in plugins for handling RESTful cross-plan links
- Closed
[BAM-2525] Ability to share working directory between different plans.
Workflow | Original: JAC Suggestion Workflow [ 3014725 ] | New: JAC Suggestion Workflow 3 [ 3606423 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Won't Do [ 10000 ] | |
Status | Original: Not Being Considered [ 11776 ] | New: Resolved [ 5 ] |
Status | Original: Gathering Interest [ 11772 ] | New: Not Being Considered [ 11776 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2700553 ] | New: JAC Suggestion Workflow [ 3014725 ] |
UIS | New: 0 |
Backlog Order (Obsolete) | Original: 6830000000 | |
Issue Type | Original: New Feature [ 2 ] | New: Suggestion [ 10000 ] |
Workflow | Original: Bamboo Workflow 2016 v1 [ 1415690 ] | New: Confluence Workflow - Public Facing v4 [ 2700553 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: Bamboo Workflow 2014 v2 [ 618638 ] | New: Bamboo Workflow 2016 v1 [ 1415690 ] |
Workflow | Original: Bamboo Workflow 2014 [ 604787 ] | New: Bamboo Workflow 2014 v2 [ 618638 ] |
Workflow | Original: Bamboo Workflow 2010 [ 205468 ] | New: Bamboo Workflow 2014 [ 604787 ] |