Closed
Bug 1179214
Opened 9 years ago
Closed 9 years ago
Stop storing the list of files changed in a revision
Categories
(Tree Management :: Treeherder: Data Ingestion, defect, P3)
Tree Management
Treeherder: Data Ingestion
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mdoglio, Assigned: emorley)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
For each revision that we store we are keeping a list of the files affected in a json string. We should stop doing that since we haven't found any use case for now.
Assignee | ||
Comment 1•9 years ago
|
||
I think one use case is bug 1059770, however:
* until we actually do that, it's pointless storing the files changed
* even when we do fix that bug, it's likely we'll only need a simplified schema - eg a combined list of files changed per push, not per revision
So I think we can still remove for now :-)
Assignee: nobody → emorley
Assignee | ||
Updated•9 years ago
|
Status: NEW → ASSIGNED
Priority: -- → P3
Summary: Consider stopping to store the list of files changed in a revision → Stop storing the list of files changed in a revision
Assignee | ||
Comment 2•9 years ago
|
||
Attachment #8630753 -
Flags: review?(mdoglio)
Reporter | ||
Updated•9 years ago
|
Attachment #8630753 -
Flags: review?(mdoglio) → review+
Comment 3•9 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder
https://github.com/mozilla/treeherder/commit/0f3d1b2bcf8700070e7e99892bf1990528811bd0
Bug 1179214 - Stop storing the list of files changed in a revision
Since we're not currently using it, and the schema we need will likely
be different if we were to start using it in the future.
Assignee | ||
Updated•9 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 4•9 years ago
|
||
Commit pushed to master at https://github.com/mozilla/treeherder
https://github.com/mozilla/treeherder/commit/7e7975d6755e981b351045957e57e2fc38f488b1
Bug 1179214 - Docs: Remove reference to a revision's 'files' property
Since it's been removed from the client/API.
You need to log in
before you can comment on or make changes to this bug.
Description
•