That's indeed a big drawback in my approach because some of my tests
uses system global semaphores.
So I have to rethink my approach :-(
Thanks for your hint.
Felix
On 2013-05-08 22:15, Dean Yu wrote:
When I was working at Yahoo!, and we started working with
Hudson/Jenkins, we originally went down this path. The issue we had
was that by running the slave inside the chroot, multiple slaves would
be contending for the same resources and capacity. We ultimately took
the approach of running the slave outside the chroots, and wrote a
BuildWrapper that intercepted each process launch to launch the
process within a designated root.
-- Dean
--
You received this message because you are subscribed to the Google Groups "Jenkins
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
