Hello,
i noticed a memory problem with my valgrind plugin for jenkins. The result
of the valgrind plugin (basically a list of errors with stacktraces) is
stored with the build (build.xml).
After a fresh restart of jenkins, those builds gets deserialized and kept
in memory as soon as the first
On 12/06/2012 09:37 AM, Johannes Ohlemacher wrote:
Why does jenkins always deserialize all builds for all jobs? My initial
(naive?) expectation was that jenkins would only deserialize a build when a
user opens it in the
browser.
That is what happens in 1.485+, or should happen at least.
Or
