Optimise LogRotator working in weak BuildReference mode

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      When -Djenkins.model.lazy.BuildReference.MODE=weak is used, Run instances are expected to be eligible for garbage collection once they are no longer in active use. The existing LogRotator implementation causes all builds of a job to be loaded, which can be very expensive in terms of memory and performance. This behavior can be improved by avoiding unnecessary build loading

            Assignee:
            Dmytro
            Reporter:
            Dmytro
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: