[Buildroot] Availability of old build results
Peter Korsgaard
jacmet at uclibc.org
Fri Dec 6 08:47:02 UTC 2013
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin at gmail.com> writes:
Hi,
> 1. During the time -next is opened (until release) we also make test
> builds on that branch (but keep the results separate from the master
> results, of course).
> Pros:
> - better visibility on the quality of -next, before it is being
> merged, and a chance to fix the problem beforehand
> Cons:
> - attention of developers is diverted away from stabilizing the
> upcoming release
> - autobuild computing capacity is diverted away too
Yeah, I'm not quite sure if this is a good idea.
> 2. Similar, in a way: when patches are posted to the list (not only
> during the stabilization month), run them through some autobuild
> configurations 'automatically' to try catching common problems (for
> example thread support, mmu support, uclibc problems, ...) and post
> the results somewhere. This generates a kind of 'staging moment' for
> patches before they get applied, to check their quality.
> Whether this should be done for all patches (even at their initial
> send) or only makes sense for patches that have been reviewed first
> (to make sure the computing power is used usefully) is something that
> can be discussed. In the latter case, we'd need to have a trigger to
> request the test builds.
This one I like! Seems like a nice little weekend task to
implement. I'll try to find time for it (but others are certainly
welcome to work on it as well)
--
Bye, Peter Korsgaard
More information about the buildroot
mailing list