At the moment Drydock policies are all global. We should facilitate policies against blueprints, to allow individual blueprints to potentially have users lease against them via Arcanist.
The scenario here is that we want developers to be able to spin up an instance so they can run commands on it (or use the other interfaces).
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Resolved | epriestley | T8089 Unprototype Harbormaster (v1) | ||
| Resolved | epriestley | T8097 Allow external systems to report results into Harbormaster | ||
| Resolved | None | T7419 Provide a straightforward way to create and update CI test statuses for a revision | ||
| Wontfix | epriestley | T4591 Allow Harbormaster to source GitHub pull requests as buildables | ||
| Resolved | epriestley | T5479 Unbeta Phragment | ||
| Duplicate | None | T7869 Support CircleCI webhooks for Test results (so that one can run unit tests asynchronously) | ||
| Resolved | epriestley | T1049 Implement Harbormaster | ||
| Wontfix | epriestley | T1816 Support downloading a compressed working copy (tar/zip) of a repository at a specific commit or tag | ||
| Resolved | epriestley | T2015 Implement Drydock | ||
| Duplicate | None | T6076 Provide infrastructure to allow users to perform leases from Arcanist |
It think it's an old project (preusmably, it was once "Drydock"?) which T2015 is tagged with, and this was created with "Create Subtask", which inherits projects.
Oh okay, I figured it was the Drydock project, but I didn't have permission to see it. I have tried looking up Drydock in the typeahead, but it doesn't come up.