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

Allow Perforce to continue using the Workspace as Working Directory when the Checkout Task is removed

    XMLWordPrintable

Details

    • 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

      If a P4 Checkout Task is used, Bamboo will consider the Working Dir to be the P4 Client Workspace.

      However, if the Checkout Task is removed and the P4 repo is used to trigger the build based on change detection, the Working Dir will be set back to the <bamboo-home>/xml-data/build-dir/ folder.

      Would be good to give the option to allow the P4 Workspace to continue to be the working Dir.

      If the Checkout Task is not being used, the Plan will still have to checkout the code somehow. And the P4 Client Workspace will still the the location for the code.

      Attachments

        Issue Links

          relates to

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

          • Closed

          Suggestion - BAM-10187 Allow specification of absolute paths for the build workspace

          • Closed

          Suggestion - BAM-9392 For the Perforce Source Repository add ability to only change directory to the Perforce workspace directory and skip sync (i.e. skip checkout/update)

          • Closed

          Activity

            People

              Unassigned Unassigned
              rbattaglin Renan Battaglin
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: