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

Improve performance of build expiry process

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Done
    • None
    • Performance
    • JDK 1.6.0_29, CentOS 5.8, MySQL 5.5

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

      Recently we found our Bamboo server disk space hitting particular free space thresholds. We configured stricter artifact retention policies for some of our more artifact-heavy plans, and increased base restrictions for the global expiry.
      While we can see the build expiry process running, it seems to taking more than a week to get through a full build expiry run, even though we've set Bamboo to run build expiry every night.
      The expiry process needs to be more performant. It seems to be a serial process, so multi-threading it would be a start.
      Additionally, instead of an expiry process kicking off at the global expiry time, it might be a possibility to have each build run the plan expiry process at the end of the build.

          Form Name

            [BAM-11711] Improve performance of build expiry process

              Unassigned Unassigned
              b0d88db9bee7 David Corley
              Votes:
              3 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: