Turns out we should implement this rather than let it sit on the roadmap indefinitely.
Revisions and Commits
- Mentioned In
- T7994: Drydock & docker
T7908: Implement aliases for objects
T182: Commit into repository directly from differential
T6076: Provide infrastructure to allow users to perform leases from Arcanist
- Mentioned Here
- T5544: Implement EC2 blueprint for Drydock
T6193: Allow Arcanist to allocate resources through Drydock
T6454: Implement support for KVM-based hosts in Drydock
T8671: Support complex resource constraints across multiple resources in Drydock
T9252: Unprototype Drydock (v1)
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: