[dmd-internals] automated merging, a status update

Brad Roberts braddr at puremagic.com
Sat Nov 16 12:33:39 PST 2013

Since this was turned on, here's the pulls that have automatically occurred.  Yay!

(2 others that I don't have the logs for, oops)
2013-11-15T22:14:32 -   calling github to merge D-Programming-Language/dmd/2773
2013-11-15T23:36:53 -   calling github to merge D-Programming-Language/dmd/2770
2013-11-16T00:58:58 -   calling github to merge D-Programming-Language/dmd/2778
2013-11-16T02:21:52 -   calling github to merge D-Programming-Language/dmd/2777
2013-11-16T03:27:19 -   calling github to merge D-Programming-Language/dmd/2765
2013-11-16T04:46:16 -   calling github to merge D-Programming-Language/dmd/2779
2013-11-16T10:26:06 -   calling github to merge D-Programming-Language/dmd/2781
2013-11-16T12:04:29 -   calling github to merge D-Programming-Language/dmd/2782

(Where's the phobos guys.. everyone asleep still?)

Currently the pace of merging is bottle necked by the slowest platform, the freebsd's.  The current 
merge criteria is that all platforms must successfully complete a run.  I'm considering changing 
that to something a little less conservative, like:

   1) 5-ish platforms must have successfully re-built against the current master
   2) all platforms must have successfully built with _a_ master + the current pull sha  (ie, 
results for out of date commits are ignored)

Too conservative still?  Not strict enough?

I'm also considering a build ordering change.  Right now master branch build have priority over pull 
builds.  What do you guys think about moving the priority to:

   1) pending merges
   2) master branch
   3) other pulls

This will eliminate a good number of builds that cost considerable time, at the potential of not 
discovering a master break quite as quickly.

Give me your thoughts on both changes.


More information about the dmd-internals mailing list