Excellent I will look for that!
On Wednesday, October 3, 2012 3:10:05 PM UTC-4, Baptiste MATHUS wrote:
>
> By the way, you don't want to keep that behaviour in mind too long (I
> mean, loading everything in memory).
>
> Thanks to Kohsuke, Jenkins is actually now gonna lazy-load build results:
>
By the way, you don't want to keep that behaviour in mind too long (I mean,
loading everything in memory).
Thanks to Kohsuke, Jenkins is actually now gonna lazy-load build results:
see
https://groups.google.com/forum/#!msg/jenkinsci-dev/ri5E9LW2kDo/G3NMc65rWpcJ
.
It's already in the trunk, so it
Rob Thanks discarding old builds seems to have done it.
On Wednesday, October 3, 2012 12:51:23 PM UTC-4, Mandeville, Rob wrote:
>
> How many runs of these builds do you have hanging around? I had this
> problem before, and it appeared that the results of every build (except for
> the log fil
How many runs of these builds do you have hanging around? I had this problem
before, and it appeared that the results of every build (except for the log
files and the artifacts) are held in memory. In my case, I stored the
environment of every build I ran and our environments get really big (a
