Official build services uses xen to build. My local instance, and presumably Luke's as well, use normal chroot builds. -- Michael -----Original Message----- From: Petit Eric [mailto:surfzoid@gmail.com] Sent: Wed 11/11/2009 2:28 PM To: luke@cray.com Cc: opensuse-buildservice@opensuse.org Subject: Re: [opensuse-buildservice] Restricting a build to certain workers hey, strange, at this time the Ubuntu 9.10 isn't working, it need some love script. You spoke about your local OBS's server ? 2009/11/11 Luke Imhoff :

I have build workers that run SLES 9 and SLES 10.  It appears that the SLES 9 worker's kernels are too old to do Ubuntu 9.10 builds, as I get this error:

FATAL: kernel too old

Is there anyway to make Ubuntu:9.10 jobs not go on SLES 9 workers to prevent this?  Right now, I just have to keep telling it to rebuild until a SLES 10 worker picks it up.

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

-- Cordially. Small Eric Quotations of the days: --------------------------------------------------------------------------- I have no special talents. I am only passionately curious -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Am Mittwoch, 11. November 2009 22:09:30 schrieb Luke Imhoff:

The official OBS doesn't even support SLES 9 because it can't run Xen, but it worked fine to build SLES 9, 10, and 11 in a chroot, which is what we needed up until this point.

You should be also fine with using eg using the SLES 11 xen and run SLES 9 builds inside. package building may brake on too old kernels, but it should (famous last words) never do on too new.

On Wed, 2009-11-11 at 15:03 -0600, Michael_E_Brown@Dell.com wrote:

...

Official build services uses xen to build. My local instance, and presumably Luke's as well, use normal chroot builds. -- Michael

-----Original Message----- From: Petit Eric [mailto:surfzoid@gmail.com] Sent: Wed 11/11/2009 2:28 PM To: luke@cray.com Cc: opensuse-buildservice@opensuse.org Subject: Re: [opensuse-buildservice] Restricting a build to certain workers

hey, strange, at this time the Ubuntu 9.10 isn't working, it need some love script. You spoke about your local OBS's server ?

2009/11/11 Luke Imhoff :

...

I have build workers that run SLES 9 and SLES 10. It appears that the SLES 9 worker's kernels are too old to do Ubuntu 9.10 builds, as I get this error:

FATAL: kernel too old

Is there anyway to make Ubuntu:9.10 jobs not go on SLES 9 workers to prevent this? Right now, I just have to keep telling it to rebuild until a SLES 10 worker picks it up.

-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Am Mittwoch, 11. November 2009 22:42:19 schrieb Michael_E_Brown@dell.com:

-----Original Message----- From: Adrian Schröter [mailto:adrian@suse.de]

...

Am Mittwoch, 11. November 2009 22:09:30 schrieb Luke Imhoff:

...

The official OBS doesn't even support SLES 9 because it can't run Xen, but it worked fine to build SLES 9, 10, and 11 in a chroot, which is what we needed up until this point.

You should be also fine with using eg using the SLES 11 xen and run SLES 9 builds inside. package building may brake on too old kernels, but it should (famous last words) never do on too new.

Problems: -- it takes time and downtime to get things upgraded

Yes, you might want to have a look in the "obs-worker-image" in our openSUSE:Tools project. We use it to build a worker image and we deploy it on all systems via PXE boot. That means I can exchange or upgrade images really in a horrible easy way. And it is quite a nice thing, that the OBS builds itself and use itself ;) There is some documentation lacking on how to setup it exactly, but I can briefly describe it if you are interessted in this way. (This hopefully develops in a delivarable 100% appliance solution in future).

-- If you are using scavenged infrastructure, you may not be able to upgrade (ie. running workers on machines purposed for other things to soak up unused cycles.)

Hm, when you do chroot builds, it might make sense to build a simple appliance which can run in xen/kvm/... on that system ..

-- Michael

-- Adrian Schroeter SUSE Linux Products GmbH email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

awesome, thanks! I have been having persistent problems with clock syncing and configure complaining about generated files being older than distributed files. This seems like a handy method to fixup both of these problems. -- Michael -----Original Message----- From: Michael Schroeder [mailto:mls@suse.de] Sent: Thu 11/12/2009 9:38 AM To: Luke Imhoff Cc: opensuse-buildservice@opensuse.org Subject: Re: [opensuse-buildservice] Restricting a build to certain workers On Wed, Nov 11, 2009 at 02:25:01PM -0600, Luke Imhoff wrote:

I have build workers that run SLES 9 and SLES 10. It appears that the SLES 9 worker's kernels are too old to do Ubuntu 9.10 builds, as I get this error:

FATAL: kernel too old

Is there anyway to make Ubuntu:9.10 jobs not go on SLES 9 workers to prevent this? Right now, I just have to keep telling it to rebuild until a SLES 10 worker picks it up.

bs_worker supports a 'hostcheck' argument where you can specify a script that can be used to check if the host can build a package. Actually it's also run after the build so that you can also check the logfile. It's called like $hostcheck --srcserver $srcserver $jobfile precheck $buildroot and $hostcheck --srcserver $srcserver $jobfile $result $buildroot/.build.log If $hostcheck exits with a non-zero return code the build will be retried on a different host. You can extract the repository from the $jobfile file. Cheers, Michael. -- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);} -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org