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

      Problem Definition

      The greatest load by far that CI systems put on SCM systems is inefficiently configured polling for changes. As an admin, I want to know the load my plan configurations are putting on my source control management system(s) so I can identify inefficient configuration and correct it.

      Suggested Solution

      Add a UI section that surfaces information about which plans are configured to poll for changes, and at what frequency. This should also show the repositories that are linked to that build plan. Optionally this could also include other SCM stats, such as average/daily fetches / clones, whether shallow clones are enabled, etc; and should show an overall picture of the activity of the instance (e.g. "Your Bamboo server is polling various SCM systems for changes a total of 1,000,000 times per day")

      This information should also be included in support zips, to enable Atlassian Support to analyse this info.

      Workaround

      Various manual database queries can be run to gather some of this information,

              Unassigned Unassigned
              dchevell Dave Chevell
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: