adam-singer / dart-carte-du-jour

Pub documentation generation system
www.dartdocs.org
Other
25 stars 8 forks source link

provide package authors visibility into why docs didn't build #36

Closed sethladd closed 10 years ago

sethladd commented 10 years ago

if a package doc failed, it is possible for the package author to determine why.

adam-singer commented 10 years ago

Yep, all being stored. We could do something similar after a post build re-generate a html or json file containing package name + package version + build log uri. Currently all build logs are available in https://console.developers.google.com/project/apps~dart-carte-du-jour/storage/www.dartdocs.org/buildlogs/

Just need to generate the mapping to which log maps to which package. A later improvement could be to narrow down the logs to a specific package+version error. As of now its the entire startup sequence, helps me with debugging issues.

sethladd commented 10 years ago

Agreed that a convention that defines the path to the logs for a particular package's build logs should be sufficient. Doesn't have to be pretty, it's just for the package author. Just easy to get and contains any errors.

adam-singer commented 10 years ago

So all build logs for specific versions will be available here. The log files are not pretty and some of them have multiple versions that fail so the user will need to grep into it. Eventually we can make them fine grained logs per package+version. http://www.dartdocs.org/failed/index.html

sethladd commented 10 years ago

Nice work!