It would be great if Diviner documentation could be generated by Harbormaster + Drydock.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | joshuaspence | T4558 Make Diviner useful for third-parties | ||
| Resolved | epriestley | T5792 Allow Diviner documentation to be generated with Harbormaster + Drydock |
Event Timeline
Comment Actions
I think doing this would require solving many of the problems that Drydock and Harbormaster solve.
For example:
- How do users configure which branches get documentation generated?
- How do you keep track of what documentation you've generated, so an older generation task doesn't overwrite it with out-of-date documentation?
- Are you going to have one working copy on disk, or several?
- If you have only one, how do you deal with it when new commits arrive more quickly than documentation generates (e.g., several branches generating docs, a new commit arrives every 20 minutes on average, docs take an hour to generate)?
- If you have more than one, how do you manage locking, allocation, cleanup and reuse?
These questions can all be answered, but I think the answers look a lot like slimmed-down versions of Harbormaster and Drydock.
Comment Actions
I don't think there's anything specifically actionable here. If your build server has direct access to the Phabricator database (it never should) I think we get this for free as soon as "lease host + build working copy + run command" is reliable.
If your build server does not have direct access to the Phabricator database (good), this is T5790 + the above.