post test results to publicly available URL

[gregcaporaso]

Would be really cool if the tests results that get emailed also were posted to the internet somewhere. Could use GitHub pages for this. If we were going to do that, we could probably also post updates to the developer documentation on a nightly basis.

[wasade]

Agree

On Thu, Sep 6, 2012 at 11:06 AM, Greg Caporaso [email protected]:

Would be really cool if the tests results that get emailed also were
posted to the internet somewhere. Could use GitHub pages for this. If we
were going to do that, we could probably also post updates to the developer
documentation on a nightly basis.

—
Reply to this email directly or view it on GitHubhttps://github.com/qiime-dev/automated_testing/issues/2.

[jairideout]

Looking into this a bit- what do you guys think about posting testing results on the Clout wiki? We could have a section for each project, and each section would have a list ordered by date with links to the results.

If other people started using Clout, they could optionally post their testing results to their own wikis.

[jairideout]

Some more info: the current size of the nightly test results is around 0.5MB. If we were to use the wiki to host these results, it would take us around 5.5 years to reach GitHub's 1GB recommended repo size limit. Seems pretty reasonable, and if we start running out of space, we could always archive older test results.

[wasade]

0.5MB tar gz'd?

[wasade]

ah...

[jairideout]

0.5MB not zipped (7 plain text files, excluding the complete log). We could store them in .tar.gz format, but I was thinking it'd be cool if they could be directly viewable online from within a web browser.

[gregcaporaso]

I definitely think it'd be good to have them viewable from a browser. What about storing them on the AWS-based web server that you're going to build?

[jairideout]

We could do that, but I like the wiki idea better, since Clout and most of the projects that it's testing are on GitHub already. That way, the testing results will also be on GitHub, under version control (in the wiki repo, which is separate from the main one), and storage/hosting is free.

We could add the ability to automatically post results to a GitHub wiki, or (optionally) store them on the machine that runs Clout.

Do you see issues with the wiki approach versus hosting them from our new web server?

[gregcaporaso]

Would the user specify which project they live under? I don't think we'd want other people's projects to show up under clout. I do worry a little about making it too GitHub specific.

[jairideout]

In the config file there'd be a way to (optionally) specify what wiki (and where) to place the results. We'd most likely add results for all of the current projects being tested on a nightly basis (e.g. QIIME, PyCogent, etc.) since they are all related bioinformatics software.

If there's an option to support a GitHub wiki and/or just save to disk, would this get around the issue of being too GitHub-specific?

[gregcaporaso]

If there's an option to support a GitHub wiki and/or just save to disk, would this get around the issue of being too GitHub-specific?

Yes, definitely - then they could just define another cron job to poll for new files and do something with them.

[gregcaporaso]

So I think you should go ahead with this solution.

[jairideout]

Great, thanks for the feedback!