Page MenuHomePhabricator

Implement Drydock
Closed, ResolvedPublic

Description

Turns out we should implement this rather than let it sit on the roadmap indefinitely.

Revisions and Commits

Abandoned
Abandoned
Abandoned
Abandoned
rPHU libphutil
Abandoned
rP Phabricator
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Abandoned
Closed
D10873
D10879
D10874
D13340
D10544
D7935
D7922
D7921
D7918
D7908
D7840
D7838
D7837
D7836
D7835
D7833
D7832
D7830
D7831
D7829
D7828
D7827
D7826

Related Objects

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
staticshock raised the priority of this task from Normal to Needs Triage.Jul 10 2014, 1:52 PM
staticshock triaged this task as Normal priority.
chad edited projects, added Drydock; removed Unknown Object (Project).Sep 11 2014, 8:37 PM

As chad advice me I would ask here.

Is it any plan (in starmap or so) to allow drydock (or harbormaster?) to lease one host and then build an launch a dockerfile, lease it and perform CI test build inside?

I'm going to close this out since I think everything here is now reasonably represented elsewhere:

  • Overall, Drydock is now nearing v1, and is likely to go into production on this host in a limited role later today.
  • The primary followup task is T9252, which will also cover logging and error recovery.

Some additional tasks:

  • EC2 support is in T5544.
  • Tasks like T6193 / T6454 cover other far-future features.
  • I'm not convinced we need to pursue working copy caches, but T8671 has some discussion if we do.