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

Adding secondary repositories to a plan should provide option to disable them as part of the build trigger

XMLWordPrintable

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

      Scenario is: Plan A has a main repository and a trigger that polls the repo; On adding repository 2, its automatically included as part of the trigger. While this may be generally desired, it can lead to significant cascading effects on downstream builds, etc.

      The option to exclude the repository from triggers, at the time of adding it as a repository, would be nice to have.

              Unassigned Unassigned
              4c7f42da203a John Knight
              Votes:
              6 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: