On 22.01.2016, at 17:44, Christopher Shanahan <[email protected]> wrote:
> So I'm tossing the question out to you guys (via an email he gave me). > Does Jenkins still hold every Job history in RAM? Was this issue fixed like > stated in the above Forum? Did the issue crop back up since then, and if so > was it fixed, or is it being worked on currently? > I'm estimating anywhere around 2,000 to 3,000 saved Job histories once 18 > months has been reached, so I want to either know I'm in the clear, or go > back to my boss with "it's not feasible to accomplish that". Jenkins discards loaded job data from memory as needed. Build data is only retained to speed things up. Of course, once you go below a certain threshold, Jenkins will keep loading builds from disk then immediately discard them to make space for other builds being loaded, so you still need _some_ memory, and having more of it makes use of Jenkins faster, but it's not like it will fail hard if you're no longer able to store all builds in RAM at the same time. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2093A039-DD6D-4D26-AB96-E4F8950D45EC%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
