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

      It would be nice to be able to monitor multiple depots/paths in Perforce for changes to trigger a build. VisualStudio projects (especially web) normally have many sub-projects that might reside under different root depots.

            [BAM-678] Allow multiple depots in Perforce connection

            I am using Bamboo 5.4.2 and I am facing the same issue for perforce. Our multiple mappings simply does not work in Bamboo. always getting exception only 3 mappings allowed !!!

            Amit Medankar added a comment - I am using Bamboo 5.4.2 and I am facing the same issue for perforce. Our multiple mappings simply does not work in Bamboo. always getting exception only 3 mappings allowed !!!

            MarkC added a comment -

            Bamboo 3.3 now supports multiple repositories and multiple Perforce depots can be used

            MarkC added a comment - Bamboo 3.3 now supports multiple repositories and multiple Perforce depots can be used

            This is very critical to us and our product(s).
            We develop a horizontal platform technology that is used across multiple vertical markets.
            The base technology is in a depot view and vertical apps that we do for specific customers are separated in another depot view.
            For any particular customer, we need to sync to changes in the base platform view and the specific customer view.
            The current single view forces our build workspace to hold EVERYTHING which becomes unwieldly.
            Please, please, please fix this as Perforce already supports multiple views using space separated specified view paths.
            Should be VERY simple to implement.

            Eric Schneider added a comment - This is very critical to us and our product(s). We develop a horizontal platform technology that is used across multiple vertical markets. The base technology is in a depot view and vertical apps that we do for specific customers are separated in another depot view. For any particular customer, we need to sync to changes in the base platform view and the specific customer view. The current single view forces our build workspace to hold EVERYTHING which becomes unwieldly. Please, please, please fix this as Perforce already supports multiple views using space separated specified view paths. Should be VERY simple to implement.

            Our depot has a number of limits on query sizes that prevent Bamboo from effectively managing workspaces. Allowing multiple roots would provide one avenue for a workaround, provided the underlying implementation of multi-root support was correct.

            Damon Kropf-Untucht added a comment - Our depot has a number of limits on query sizes that prevent Bamboo from effectively managing workspaces. Allowing multiple roots would provide one avenue for a workaround, provided the underlying implementation of multi-root support was correct.

            Would be useful for me too, as we have both development and environment folders, both of which need to be checked out and monitored for a build.

            I've worked around this in the meantime by moving the environment under development, but our build team is displeased with this "solution".

            David Dunwoody added a comment - Would be useful for me too, as we have both development and environment folders, both of which need to be checked out and monitored for a build. I've worked around this in the meantime by moving the environment under development, but our build team is displeased with this "solution".

              Unassigned Unassigned
              bcf7d899afec MattyJ
              Votes:
              13 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: