Am Mittwoch, 11. Dezember 2013, 14:52:16 schrieb Michal Marek:
Dne 11.12.2013 12:07, Adrian Schröter napsal(a):
Am Mittwoch, 11. Dezember 2013, 11:39:21 schrieb Michal Marek:
Dne 11.12.2013 10:54, Adrian Schröter napsal(a):
I assume that we agree that such breakages should not appear first time in Factory, right?
Yes. I only do not like the bootstrap (or whatever you call it) in all projects that build the kernel.
hm, this is how we work with all other packages, except the kernel.
Please do not exaggerate. Most other packages are not needed to build themselves.
okay, most of the _bootstrap_ packages are needed to build themselves. (and some more)
We want to use the build result to be able to verify it. And given our test driven development model, we want to see the effect before we merge submissions.
We could even add some kind of additional QA package beside and, for example, check the kernel interface (eg. POSIX compliance) if we have such tests.
I can add a kernel-qa.spec to the kernel git if you like. But only as long as this is a leaf package.
Hm, makes only sense when the kernel-build-obs package would be also part of kernel git and Kernel projects, otherwise this package would have no effect. Question is if we have test cases which would make sense to run automatically inside of VM's, but I am told by QA that there are some which can be applied. We do check already on submit requests, if all spec files in that package does successfull build. So we would verify automatically on a submit request to Factory, if checks in kernel-qa were successful. But again, this does currently rely that all spec files are comming from one package container.
So you say basically we need another QA project somewhere where all kernel & tool chain shall be tested before submission to factory, right? So Kernel:$branch projects stay as kernel-only projects, but the devel project for factory will become some other project?
That can certainly be done. I didn't think much about Factory in my previous email, but more about the released products and SLE betas. The factory kernels are nowadays submitted by a daily cronjob, so a _separate_ staging project which does the bootstrap makes sense here.
So, in effect this staging project would replace Kernel:HEAD as devel project for openSUSE:Factory?
Yes, that sounds logical.
Hm, so the workflow would be commiting kernel-source to Kernel:HEAD, submiting to Kernel:QA and from there to openSUSE:Factory? -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org