[opensuse-factory] staging concepts
Hello, All. I don't completely understand staging concepts. Now we have stage for new kernel version. But It is not built for arm. How should we now that new kernel won't brake factory:arm? Currently, kernel is broken fir arm. -- Best regards! Posted using Hotdoged on Android -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04.02.2014 10:30, Matwey Kornilov wrote:
Hello, All.
I don't completely understand staging concepts.
Now we have stage for new kernel version. But It is not built for arm. How should we now that new kernel won't brake factory:arm? Currently, kernel is broken fir arm.
Hi, The plan is to work from easy to hard. Right now I'm checking that the two inner rings stay green for i586 and x86_64 and pass minimal automated testing on x86_64 in kvm. Even that means a lot can break without us noticing - but at least we have a base we can rely upon. This works with a lot of manual input from my side now for over a month, and we[1]'re working on automating this step. Once that's done, we can move to new targets. There are several candidates on what to tackle afterward: - ports (if you can provide automated test cases within openQA and enough build power, that should be fairly trivial) - Keeping live cds / desktops tested all the time - add more testing to the core rings As I tried to explain in the past: adding staging projects doesn't do magic and won't solve things on their own. If the kernel is broken for arm and nothing tests it, it will be broken in the future. Even the staging projects right now only test that the kernel survives one installation and one reboot and that's basically it. Greetings, Stephan [1] https://progress.opensuse.org/projects/stagings/issues -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Dienstag, 4. Februar 2014, 14:15:59 wrote Stephan Kulow:
On 04.02.2014 10:30, Matwey Kornilov wrote:
Hello, All.
I don't completely understand staging concepts.
Now we have stage for new kernel version. But It is not built for arm. How should we now that new kernel won't brake factory:arm? Currently, kernel is broken fir arm.
Hi,
The plan is to work from easy to hard. Right now I'm checking that the two inner rings stay green for i586 and x86_64 and pass minimal automated testing on x86_64 in kvm. Even that means a lot can break without us noticing - but at least we have a base we can rely upon.
This works with a lot of manual input from my side now for over a month, and we[1]'re working on automating this step. Once that's done, we can move to new targets. There are several candidates on what to tackle afterward:
- ports (if you can provide automated test cases within openQA and enough build power, that should be fairly trivial) - Keeping live cds / desktops tested all the time - add more testing to the core rings
As I tried to explain in the past: adding staging projects doesn't do magic and won't solve things on their own. If the kernel is broken for arm and nothing tests it, it will be broken in the future. Even the staging projects right now only test that the kernel survives one installation and one reboot and that's basically it.
Greetings, Stephan [1] https://progress.opensuse.org/projects/stagings/issues
Can me someone give me some insight about the osc plugins you write for this? Just from my gut feeling this might be a problem to make this as osc only and even as plugins only. Because others may not be able to follow these workflows then or to see states when using other clients. What are these plugins doing exactly? -- 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-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04.02.2014 17:17, Adrian Schröter wrote:
Can me someone give me some insight about the osc plugins you write for this?
Just from my gut feeling this might be a problem to make this as osc only and even as plugins only. Because others may not be able to follow these workflows then or to see states when using other clients.
What are these plugins doing exactly?
https://github.com/coolo/factory-auto is the source for the plugins - but we're still in the process of redefining what we need. And yes, I agree having this as osc plugins is only useful during the research phase. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 04.02.2014 17:22, Stephan Kulow wrote:
On 04.02.2014 17:17, Adrian Schröter wrote:
Can me someone give me some insight about the osc plugins you write for this?
Just from my gut feeling this might be a problem to make this as osc only and even as plugins only. Because others may not be able to follow these workflows then or to see states when using other clients.
What are these plugins doing exactly?
https://github.com/coolo/factory-auto is the source for the plugins - but we're still in the process of redefining what we need. And yes, I agree having this as osc plugins is only useful during the research phase.
Little update: we moved the plugin sources to https://github.com/openSUSE/osc-plugin-factory - factory-auto is now only my toys again ;) Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Adrian Schröter -
Matwey Kornilov -
Stephan Kulow