[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[MirageOS-devel] is_mirage_broken on openmirage.org

Hi all, one of the items discussed in yesterday's call was about having a more visible outcome for is_mirage_broken [1] -- the service that tries to build a set of mirage applications for different targets.

Currently, it generates a Markdown file summarising the outcome of each build attempt [2]. One idea was to use this Markdown on a page served by openmirage.com

I experimented with this in a change to mirage-www [2] which, unless I'm mistaken, generates the image that serves openmirage.com. The change consists of an additional wiki page on openmirage.org that contains the Markdown generated by is-mirage-broken, as can be seen from the diff [2].

I'm writing to poll the list for your thoughts on whether this is a reasonable change.

If I get the go-ahead, I can modify crons.sh (the main script) in is-mirage-broken to push the generated Markdown file to our mirage-www repo, to update the wiki page. There is some implicit git state that the script relies upon (i.e., which repository is being pushed to) that I'd need to make explicit (since the script would be dealing with two, not one, repositories after this change: is-mirage-broken and mirage-www).

Best wishes,

[1] https://github.com/mirage/is-mirage-broken/
[2] https://github.com/mirage/is-mirage-broken/blob/master/logs/README.md [3] https://github.com/niksu/mirage-www/commit/cf7dc0947d1d356b1aea5ca2ed709042d33d96c9

MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.