The GitPlugin does not garbage collect automatically, thus doesn't optimize disk space utilization and good operating performance.

      I have set up a build triggering a shell-script to do this every night, but don't you think it should be a feature of the GitPlugin?

          [JENKINS-13493] GitPlugin should garbage collect

          Stein Inge Morisbak created issue -
          Stein Inge Morisbak made changes -
          Description Original: The GitPlugin does not garbage collect automatically, thus doesn't optimize disk space utilization and good operating performance.

          There should also be an option to prune branches

          I have set up a build triggering a shell-script to do this every night, but don't you think it should be a feature of the GitPlugin?
          New: The GitPlugin does not garbage collect automatically, thus doesn't optimize disk space utilization and good operating performance.

          I have set up a build triggering a shell-script to do this every night, but don't you think it should be a feature of the GitPlugin?
          Nicolas De Loof made changes -
          Issue Type Original: Improvement [ 4 ] New: New Feature [ 2 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 143959 ] New: JNJira + In-Review [ 176043 ]

          Is this still in review?

          We just had a issue where the .git folder had so much leftover in it that it started to give problems in the Jenkins master.

          Running

          {{git gc --prune=now }}

          manually solved it.

          An option to have this done by Jenkins would be nice.

           

           

           

          Quentin Nerden added a comment - Is this still in review? We just had a issue where the .git folder had so much leftover in it that it started to give problems in the Jenkins master. Running {{git gc --prune=now }} manually solved it. An option to have this done by Jenkins would be nice.      

          Stephan Krull added a comment -

          @Attendees: Whatever the usual process is with git-plugin related issues: This one should really be replanned. Can you pls take care to get it into a proper review and planning? Thank you.

          Stephan Krull added a comment - @Attendees: Whatever the usual process is with git-plugin related issues: This one should really be replanned. Can you pls take care to get it into a proper review and planning? Thank you.

          +1

          Paweł Alikowski added a comment - +1
          Nicolas De Loof made changes -
          Assignee Original: Nicolas De Loof [ ndeloof ]

          +1

          This problem exists both on the master and on the slaves. In our case we had a git repo on the master node with 299GB. After manually running git gc it was reduced to 1.5GB. This repo naturally gets checked out very very regularly just to find the pipeline script and then delegate it to a node (where the repo is checked out once more).. So this should be done during all checkouts, both on master (for pipeline file) and on the slaves (during normal build).

          Matthias Keller added a comment - This problem exists both on the master and on the slaves. In our case we had a git repo on the master node with 299GB. After manually running git gc it was reduced to 1.5GB. This repo naturally gets checked out very very regularly just to find the pipeline script and then delegate it to a node (where the repo is checked out once more).. So this should be done during all checkouts, both on master (for pipeline file) and on the slaves (during normal build).

            Unassigned Unassigned
            steinim Stein Inge Morisbak
            Votes:
            15 Vote for this issue
            Watchers:
            23 Start watching this issue

              Created:
              Updated: