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

Allow specification of absolute paths for the build workspace

    XMLWordPrintable

Details

    • 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.

    Description

      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.

      Attachments

        Issue Links

          is related to

          Suggestion - BAM-10051 Allow Perforce to continue using the Workspace as Working Directory when the Checkout Task is removed

          • Closed
          relates to

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

          • Closed

          Activity

            People

              Unassigned Unassigned
              675f116f79b3 Zachary Roadhouse
              Votes:
              5 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: