Fyi it's possible to view the results of a `Doc` build on try by visiting this link: http://gecko-docs.mozilla.org-l1.s3-website.us-west-2.amazonaws.com/ So if reviewbot were to run the `DocUp` task, it could post the link as a comment. The main issue is that try pushes will overwrite one another, so we'd need to modify the `DocUp` task to upload files to a namespace keyed by the push revision (and set an expiry of a week or so).
Bug 1643293 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Fyi it's possible to view the results of a `DocUp` build on try by visiting this link: http://gecko-docs.mozilla.org-l1.s3-website.us-west-2.amazonaws.com/ So if reviewbot were to run the `DocUp` task, it could post the link as a comment. The main issue is that try pushes will overwrite one another, so we'd need to modify the `DocUp` task to upload files to a namespace keyed by the push revision (and set an expiry of a week or so).
Fyi it's possible to view the results of a `DocUp` build on try by visiting this link: http://gecko-docs.mozilla.org-l1.s3-website.us-west-2.amazonaws.com/ So if reviewbot were to run the `DocUp` task, it could post the link as a comment. The main issue is that try pushes will overwrite one another, so we'd need to modify the `DocUp` task to upload files to a namespace keyed by the push revision (and set an expiry of a week or so). Shouldn't be too hard to do.