Purge old test data from github

RESOLVED WONTFIX

Status

Socorro
General
RESOLVED WONTFIX
6 years ago
5 years ago

People

(Reporter: jberkus, Assigned: laura)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
Current a git clone of socorro takes a really long time, because we need to clone around 150MB.  Most of that 150MB is obsolete test data, dating back to socorro 1.1, in the form of very large tarballs.

We should rm those tarballs and purge them from the git history so that they stop bloating our clones.
(In reply to [:jberkus] Josh Berkus from comment #0)
> Current a git clone of socorro takes a really long time, because we need to
> clone around 150MB.  Most of that 150MB is obsolete test data, dating back
> to socorro 1.1, in the form of very large tarballs.
> 
> We should rm those tarballs and purge them from the git history so that they
> stop bloating our clones.

Seems doable, but we'd have to rebase master which is kind of icky.

Doesn't git support sparse checkouts now? Have you looked into that at all?
(Assignee)

Updated

6 years ago
Target Milestone: 2.4 → ---
Component: Socorro → General
Product: Webtools → Socorro
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX

Comment 2

5 years ago
For future reference -- if you need a shallow checkout, there is a flag: `git clone --depth=50`
You need to log in before you can comment on or make changes to this bug.