Re: [MirageOS-devel] is_mirage_broken on openmirage.org

[Nik Sultana <ns441@xxxxxxxxx>]

On 2014-10-29 10:36, Anil Madhavapeddy wrote:
> That sounds good. If you install the GitHub OPAM package, there is a
> command line utility that creates a pull request. If one is only
> created when the status changes, that should be pretty low traffic (I
> hope).
>
> Anil
Currently the status page is changed every time Bactrian runs, since the 
time on the page is updated to indicate that the page is fresh. I could 
set things up to continue updating the page in this way in the 
is-mirage-broken repo, but to avoid generating a PR to mirage-www unless 
the status of some build target has changed.
Nik

> > On 29 Oct 2014, at 09:52, Nik Sultana <ns441@xxxxxxxxx> wrote:
> >
> > 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,
> > Nik
> >
> > [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
> > MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
> > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel