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

Allow One Plan To Be Based On Multiple CVS Modules

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 3.3
    • Repository (CVS)
    • None
    • 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.

      Please allow multiple CVS modules to be listed as the module for a CVS-based plan. The use-case for this is CVS repository with code broken into multiple modules, where one particular component wants to be tested but other modules (such as 'lib') are required.

      Our CVS repository, for example, has top-level modules named: core, gui, lib, tests, and components. We also have an amper-module called 'limewire' that has some additional top-level data and then references those. For Bamboo, we have three plans: LW-COMPILATION, LW-NIGHTLY, and LW-COMPONENTS. The compilation plan just checks that all the code compiles and runs whenever anything in the 'limewire' module changes. We can't run all the tests all the time because they take too long to run. The nightly plan runs every night and runs the full test suite. The components build is where the problem lies.

      The components module requires the lib module is checked out as a sibling, and references those files. To workaround this, I created an amper-module that gets both components & lib. It would be nice if this workaround were not required, and Bamboo would allow multiple modules per plan.

            [BAM-1015] Allow One Plan To Be Based On Multiple CVS Modules

            MarkC added a comment -

            Bamboo 3.3 now supports multiple repositories

            MarkC added a comment - Bamboo 3.3 now supports multiple repositories

            rkrzewski added a comment -

            IMO much more frequent use case than multiple repositories per plan would be multiple modules (directories) from the same repository per plan.
            Moreover it can probably be implemented with less effort - UI change is trivial, just let the modules be enumerated as coma separated list, and modules list needs to be iterated upon during poll / update / checkout.
            Therefore I would suggest tackling this issue before BAM-1868 / BAM-955

            rkrzewski added a comment - IMO much more frequent use case than multiple repositories per plan would be multiple modules (directories) from the same repository per plan. Moreover it can probably be implemented with less effort - UI change is trivial, just let the modules be enumerated as coma separated list, and modules list needs to be iterated upon during poll / update / checkout. Therefore I would suggest tackling this issue before BAM-1868 / BAM-955

            Brett Adam added a comment -

            This needs to be generalized to be "allow multiple source repositories per plan" not just for CVS. We have need for multiple disparate sources of change to be considered as trigger sources for builds. I'm filing another issue for the generalized case.

            Brett Adam added a comment - This needs to be generalized to be "allow multiple source repositories per plan" not just for CVS. We have need for multiple disparate sources of change to be considered as trigger sources for builds. I'm filing another issue for the generalized case.

              mwent Marek Went (Inactive)
              392fb6eb772b Sam Berlin
              Votes:
              16 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: