On 14 May 2013 21:52, Kevin Hilman <khil...@linaro.org> wrote: > 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.)
https://wiki.linaro.org/Platform/Infrastructure/infrastructure-knowledgebase#ci.linaro.org but I believe it's now partly outdated. > I use my own jenkins setup for some of my stuff, and scripts for the > rest, but it would be ideal to not have to duplicate effort here. > > A quick scan of https://ci.linaro.org/jenkins/view/kernel-ci makes me > realize there is nothing terribly helpful there (based on reasons Nico > already pointed out), but it has peaked my curiosity on the Jenkins > changes/plugins being used. > > 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. You've got access and can even view/modify the set up. I used a multi-configuration project for these jobs. If you have more questions, just ask. Cheers, Fathi _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
