[JENKINS-76075] Optimise LogRotator working in weak BuildReference mode

[jenkins-infra-bot]

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

---

Originally reported by dukhlov, imported from: Optimise LogRotator working in weak BuildReference mode

• assignee: dukhlov
• status: Closed
• priority: Minor
• component(s): core
• label(s): 2.528.1-rejected, 2.528.2-rejected, 2.528.3-fixed
• resolution: Fixed
• resolved: 2025-09-23T01:49:08+00:00
• votes: 0
• watchers: 4
• imported: 2025-11-24

Raw content of original issue

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