Bug 1623596 - Git plugin might be suffering from memory leak
Summary: Git plugin might be suffering from memory leak
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: project-infrastructure
Version: mainline
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-29 17:32 UTC by Yaniv Kaul
Modified: 2020-03-12 12:53 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-12 12:53:43 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github https://github.com/jenkinsci git-plugin pull 578 0 None None None 2018-10-03 09:20:28 UTC

Description Yaniv Kaul 2018-08-29 17:32:27 UTC 
Description of problem:
It provides a warning and a hint to look at https://wiki.jenkins.io/display/JENKINS/Remove+Git+Plugin+BuildsByBranch+BuildData to workaround it.
Comment 1 M. Scherer 2018-08-29 19:59:24 UTC 
So, that do not seems like a memory leak, but that would solve our disk space issue in a elegant way. It should also solve by itself with 3.0 version of the git plugin, currently in beta.

I guess we can first clean the branch with the groovy script, that would give use some more breathing room, and later wait for the upgrade ?
Comment 2 Nigel Babu 2018-10-03 09:20:28 UTC 
Adding the Github link to track the pull request which fixes this.
Comment 4 Worker Ant 2020-03-12 12:53:43 UTC 
This bug is moved to https://github.com/gluster/project-infrastructure/issues/33, and will be tracked there from now on. Visit GitHub issues URL for further details
Note You need to log in before you can comment on or make changes to this bug.