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
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
Hi Stephen
Thanks for the hint, the second one looks good but I have to check this
with the
admin of the buildserver.
In the meanwhile I launch the slave via command on master. The master
ssh-s to the
slave and starts the slave.jar in the chroot via a script. Seems to work
properly...
On 0
Can you run a ssh-server in the chroot environment? or better yet, can you
create a user on the build slave that is always logged in within the chroot
environment?
With the former you just connect to the chroot's ssh-server port. With the
latter you just connect as the chroot'ed user
On 18 April
I have a buildserver (ubuntu 12.04) and need to run a jenkins slave on
that server
in a (s)chroot environment.
Question: How can I set up a slave that runs directly in the
chroot-environment on that
buildserver?
I mean, who can I achieve that jenkins master connects directly into the
chroot?
