https://bugzilla.wikimedia.org/show_bug.cgi?id=48025
--- Comment #18 from Antoine "hashar" Musso <[email protected]> --- After a bit more investigation, our build.xml files contains references to org.jvnet.hudson.plugins.DownstreamBuildViewAction which was a plugin to display the dependencies between builds. When upgrading Jenkins I have removed that plugin but the build files still contains references to it such as: <org.jvnet.hudson.plugins.DownstreamBuildViewAction> <build class="build" reference="../../.."/> </org.jvnet.hudson.plugins.DownstreamBuildViewAction> When Jenkins parse the build history, it will detect this is no more used and will log a message which is stored in memory. The data can be discarded manually via the 'Manage old data' https://integration.wikimedia.org/ci/administrativeMonitor/OldData/manage With the thousands of build history, the old data store turns out to have too many item for Java heap size and that most probably cause the memory exhaustion. The slow way to solve that is to ask Jenkins to parse the history files for a job then manually discard all data. The fastest / hard way would be to parse all the build.xml and remove the XML snippet. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
