+++ Kevin Hilman [2013-05-14 11:52 -0700]: > Nicolas Dechesne <nicolas.deche...@linaro.org> writes: > > > On Thu, May 9, 2013 at 7:56 PM, Fathi Boudra <fathi.bou...@linaro.org>wrote: > > > >> > Hi all, > >> > > >> > I just wanted to forward this thread from LAKML to linaro-dev: > >> > http://article.gmane.org/gmane.linux.ports.tegra/10683 > >> > > >> > Seems there is lots desire for an improvement to automated build > >> > coverage and automated reporting along with it. > >> > >> I replied to it. We've got already such daily builds with boot > >> testing: https://ci.linaro.org/jenkins/view/kernel-ci > >> > >> I'm surprised that some people involved in Linaro and this thread > >> didn't mentioned it.
> > I have to admit that what we do in terms of Kernel CI is still a bit fuzzy > > to me, even now that I am an insider. > > I'll second Nicolas' comments. > > As a kernel developer and upstream maintainer (and now working for > Linaro), it's not at all clear (or documented that I can find) how > kernel CI is being structure and implemented nor how it could be useful > for kernel developers and especially maintainers (who are *very* > interested early notification of build/boot failures for various > defconfigs and even non-ARM arch builds.) > Is there a way for us (linaro folks) to see more of the Jenkins setup > for these jobs (including the scripts.) There appears to be some useful > add-ons being used. Read-only access to the detailed configuration of > the jenkins jobs would be very useful. I've been mugged into improving our CI, with initial focus particularly on kernels, so I'm actually quite keen to hear what people actually want/need, and why they aren't using it currently (if they aren't). Speed of builds is one thing that's obviously in need of improvement and that's coming very soon, but there are no doubt other issues. I'll set up a session at Connect Dublin on this so we can have a brainstorm, and people can get a better idea of what we have already. But obviously feel free to continue this thread or poke me directly. There is certainly plenty of stuff we can make faster/clearer/more useful. I've so far got as far as working out how the Jenkins part of it works and implementing faster ubuntu kernel builds (by crossing them instead of native-building on canonical PPAs) (I'm still kicking this, but I hope it'll be running any day now), but there is piles of other stuff that only Fathi and the Lava people understand currently :-) Glad to hear that some people do actually care and want to use this stuff... Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
