Page MenuHomePhabricator
Create Task
Maniphest T9872

Give Drydock Working Copies useful names
Closed, InvalidPublic
Actions

Description

This is pretty useless:

pasted_file (915×550 px, 90 KB)

I can't tell what host each working copy is running on, nor the repositories it has cloned. Since working copies never expire, I'll need to at some point go and clean these up. In order to determine which ones need cleaning up, I want to be able to know which repositories they've cloned (so I can clear out old ones).

(The details on each resource show the raw PHIDs for host leases / repos, but those can't be lined up with anything useful in the web UI).

Related Objects

Event Timeline

hach-que created this task.Nov 30 2015, 3:25 PM
hach-que raised the priority of this task from to Needs Triage.
hach-que updated the task description. (Show Details)
hach-que added a project: Drydock.
hach-que updated the task description. (Show Details)
hach-que updated the task description. (Show Details)
hach-que added a subscriber: hach-que.
epriestley moved this task from Backlog to Future on the Drydock board.Nov 30 2015, 4:39 PM
epriestley closed this task as Invalid.Nov 30 2015, 4:44 PM
epriestley claimed this task.
epriestley added a subscriber: epriestley.

I'll need to at some point go and clean these up.

Why? File a task about the root problem instead. See Contributing Feature Requests.

hach-que added a comment.Nov 30 2015, 10:39 PM

Because I have a lot of repositories, and there are multiple copies of each repository (because things are running in parallel), I will run out of disk space if I have multiple full copies of every repository in Phabricator kept on the build hosts for all time.

These build hosts sit on physical hardware, not EC2, so I can't just increase the disk storage magically.

hach-que mentioned this in T9875: Build hosts run out of disk space because Drydock doesn't clean up working copies automatically.Dec 1 2015, 12:02 AM
Phabricator · Built by Phacility