Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-2525

Ability to share working directory between different plans.

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • Builds
    • None
    • 0

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      From BSP-749

      Imagine I have two projects or plans:
      ProjA-Build
      ProjA-Test

      The 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)

            [BAM-2525] Ability to share working directory between different plans.

            Krystian Brazulewicz added a comment -
            Atlassian Update – [11 April 2019]

            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 understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritise other areas of the Bamboo roadmap, including:

            1. Performance and stability improvements
            2. Providing building blocks for High Availability and Disaster Recovery solutions
            3. Improving permission system
            4. Allowing per-project allocation of resources
            5. Improving Bitbucket Server and Jira integrations

            We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

            To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

            Kind regards,
            Bamboo Team

            Krystian Brazulewicz added a comment - Atlassian Update – [11 April 2019] 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 understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritise other areas of the Bamboo roadmap, including: Performance and stability improvements Providing building blocks for High Availability and Disaster Recovery solutions Improving permission system Allowing per-project allocation of resources Improving Bitbucket Server and Jira integrations We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Bamboo Team

              Unassigned Unassigned
              aca233f59075 Kirk Wylie
              Votes:
              6 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: