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

Bamboo does not pick up changes from Perforce mapped depot locations to a single client using +//depot/myDepot

    XMLWordPrintable

Details

    Description

      If a p4 client is mapped like

      //depot/Prj/... //newClient/depot/Prj/...
+//depot/Dep/... //newClient/depot/Prj/Dep/...

      and the plan's repository configuration | Depot View is

      //newClient/depot/Prj/...

      no changes to files in //newClient/depot/Prj/Dep/... are picked up by change detection.
      The way the change detection (PerforceManager.java) works now is that the client view is mapped to the depot view. Thus 

      p4 changes //depot/Prj/...

      is used.
      What should be used is 

       p4 changes  //newClient/depot/Prj/...

      which is the client view
      This will detect changes in //newClient/depot/Prj/Dep/...

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. BAM-7667 Perforce repository changes are not detected if "+" mapping is used

          • Low - Low priority issues
          • Closed
          was cloned as

          Suggestion - BAM-3669 Bamboo p4 implementation should process all client spec definition settings

          • Gathering Interest

          Activity

            People

              Unassigned Unassigned
              ukuhnhardt Ulrich Kuhnhardt [Atlassian]
              Votes:
              18 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: