On 2/1/15 3:10 AM, Erik Rijkers wrote:
> I find myself once again trying to find and extract links to the latest patch, from
https://commitfest.postgresql.org/(or
> anywhere on postgresql.org; the mail archive being another possibility). The goal, of course, is to automatically
download
> & compile the lot.
>
> I suppose I can figure it out but before I go any further: wouldn't it be possible to build some support for that
goalin
> the commitfest application (or saomewhere else)? Could it be done by pulling the latest link for each patch for each
fest
> to some central place/list/ page? It could be more stable then my local hacking.
>
> (Almost equally satisfying would be to receive a program from anyone who has already done the work of extracting
linksfrom
> those pages or the mail archive)
https://github.com/petere/commitfest-tools/blob/master/commitfest_branches#L134
Note, however, that this kind of thing needs constant manual
baby-sitting, because people send all kinds of attachments in all kinds
of ways.
Example 1: Someone sends patch and benchmark output as two attachments
with indistinguishable content types.
Example 2: Mail with two patches that are alternative implementations
(so they don't apply together), as opposed to mail with two patches that
apply in series.
The only way to fix these kinds of fundamental issues is using git pull
requests.
Nonetheless, the above code works most of the time. I have used it for
automatically building and compiling commit fest submissions
(http://petereisentraut.blogspot.com/2013/08/automating-patch-review.html),
but got tired of having to manually feed the build failures to the
mailing list. I need a way to automatically post build results back
into the commit fest app.