[opensuse-buildservice] obs-worker cleanup chroot build environment / after build script
Hello,
related to the "obs-worker - restarting services in chroot env at build time" mailing we still have some problems to get a more or less "clean" chroot build environment on a dedicated obs-worker machine.
Therefore the question: Is there an (scripting) entry point to cleanup the obs-worker chroot build environment after _every_ build of a package even if the build has failed?
In our case we have to kill some services like mysql or apache2 to ensure that they aren't running accidently after a (failed) build on the obs-worker.
Your help is again very much appreciated.
On Wednesday 2012-07-25 10:25, Florian Kabus wrote:
Hello,
related to the "obs-worker - restarting services in chroot env at build time" mailing we still have some problems to get a more or less "clean" chroot build environment on a dedicated obs-worker machine.
Therefore the question: Is there an (scripting) entry point to cleanup the obs-worker chroot build environment after _every_ build of a package even if the build has failed?
In our case we have to kill some services like mysql or apache2 to ensure that they aren't running accidently after a (failed) build on the obs-worker.
Your help is again very much appreciated.
Having the worker spawn a virtual machine (OBS can do it) "fixes" this in a manner of speaking. Arguably, with the advent of cgroups, killing leftover processes should be possible even without the VM trick, but I don't see obs-worker supporting this cgroup exploitation yet.
Hi there,
thanks for your suggestion. Right now we don't have the possibility of a virtual obs-worker build environment.
Therefore we have solved the issue with a more or less dirty hack in the build script. We kill the services leftover at the end of the cleanup_and_exit function.
Greetings
Am 05.09.2012 03:49, schrieb Jan Engelhardt:
On Wednesday 2012-07-25 10:25, Florian Kabus wrote:
Hello,
related to the "obs-worker - restarting services in chroot env at build time" mailing we still have some problems to get a more or less "clean" chroot build environment on a dedicated obs-worker machine.
Therefore the question: Is there an (scripting) entry point to cleanup the obs-worker chroot build environment after _every_ build of a package even if the build has failed?
In our case we have to kill some services like mysql or apache2 to ensure that they aren't running accidently after a (failed) build on the obs-worker.
Your help is again very much appreciated.
Having the worker spawn a virtual machine (OBS can do it) "fixes" this in a manner of speaking. Arguably, with the advent of cgroups, killing leftover processes should be possible even without the VM trick, but I don't see obs-worker supporting this cgroup exploitation yet.
On Wed, Sep 05, 2012 at 10:20:52AM +0200, Florian Kabus wrote:
thanks for your suggestion. Right now we don't have the possibility of a virtual obs-worker build environment.
Therefore we have solved the issue with a more or less dirty hack in the build script. We kill the services leftover at the end of the cleanup_and_exit function.
FYI: There's the 'killchroot' script used in the build package if you do a 'build --kill', but you're probably already using it.
Cheers, Michael.
buildservice@lists.opensuse.org
-
Florian Kabus -
Jan Engelhardt -
Michael Schroeder