Closed
Bug 1452758
Opened 7 years ago
Closed 7 years ago
Generate tc-worker docs in an installer-compatible fashion
Categories
(Taskcluster :: Services, enhancement)
Taskcluster
Services
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: dustin, Assigned: wcosta)
Details
https://github.com/taskcluster/taskcluster-worker/blob/78f17374b3813997f66b7c0e9ec1350524184260/.taskcluster.yml#L225-L251 does some partial generation of docs, but then relies on upload-project-docs from taskcluster-lib-docs for the rest.
The two "new" ways of building docs in taskcluster-installer are:
- run the equivalent of upload-project-docs on the checked-out repo
- invoke a simple 'write-docs' endpoint on the app to generate a compatible tarball
This doesn't really fit either mold. Rather than replicate the .taskcluster.yml functionality (differently) in a special-case in taskcluster-installer, can we make taskcluster-worker use one of the two ways given above?
Probably the ideal would be to have taskcluster-installer build the tc-worker docker images, and then call `DOCS_OUTPUT_DIR=/foo docker run taskcluster-worker write-docs` similar to how it does for services. Maybe that uses some taskcluster-lib-docs-go library, too?
https://github.com/taskcluster/taskcluster-worker/commit/78f17374b3813997f66b7c0e9ec1350524184260 temporarily gets things building again.
Updated•7 years ago
|
Assignee: jopsen → wcosta
| Reporter | ||
Comment 1•7 years ago
|
||
We don't need this if we're not supporting tc-worker :D
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
Updated•6 years ago
|
Component: Redeployability → Services
You need to log in
before you can comment on or make changes to this bug.
Description
•