Project

General

Profile

Bug #20221

larsim repository is >2GB big

Added by Gianluca Petrillo over 1 year ago. Updated about 1 year ago.

Status:
Assigned
Priority:
Normal
Assignee:
Category:
Other
Target version:
-
Start date:
06/25/2018
Due date:
% Done:

0%

Estimated time:
Occurs In:
Experiment:
-
Co-Assignees:
Duration:

Description

Please remove whatever in the repository history was there, should have not been there and is making future generations pay for it.

History

#1 Updated by Marc Mengel over 1 year ago

Okay, so I know how to clean the repository, we send a script through cleaning out the .root files from all history for all time, and this will take the repository back to a reasonable size.

However, this changes the commit hash id's all the way up the chain from quite some time ago on develop and master, which means anyone who has a clone of the repository who doesn't similarly clean it out can push the stuff back in.

So we need to:

  • get everyone who has it checked out to:
    • git flow publish any branch they are working on
    • git commit their changes
    • git push
    • remove their local copy
  • scrub the cdcvs copy of the repository
  • folks can git clone it again.

Otherwise we will keep having people inadvertently pushing this stuff back into
the repository, and being confused about where branches actually are, etc.

#2 Updated by Lynn Garren over 1 year ago

  • Status changed from New to Under Discussion

We have already reduced the repository sized from 11 GB to it's present 2.3 GB. However, it appears that certain actions result in inadvertently pushing the old history again. We will discuss the problem and solution at the next coordination meeting.

#3 Updated by Katherine Lato over 1 year ago

Marc Mengel presented options at the July 3rd Coordination meeting - https://indico.fnal.gov/event/17502/contribution/3/material/slides/0.pdf
Further discussion is needed to finalize the plan.

#4 Updated by Katherine Lato over 1 year ago

We have a filter that should prevent most probably causes of the problem. We can create a new repository with a different name, same content. It will be a breaking change, however it's very scriptable.

#5 Updated by Kyle Knoepfel about 1 year ago

  • Status changed from Under Discussion to Assigned
  • Assignee set to Erica Snider

Erica will send out an email.



Also available in: Atom PDF