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 On Monday, April 22, 2013 11:52:53 AM UTC-7, flx wrote: > > 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 04/19/2013 10:42 AM, Stephen Connolly wrote: > > 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 2013 19:57, felix schwitzer <flx...@yahoo.de <javascript:>>wrote: > >> 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? >> >> Background: >> My jenkins project is a multiconfiguration project that runs on different >> slaves, some slaves are >> simple linux boxes without a chroot-environment, others need the chroot. >> Therefore I try to >> avoid entering into the chroot in each build step, because the job >> configuration becomes really >> complex; If I enter the chroot in the build steps, I have to change into >> the chroot conditionally, >> depending on the slave that builds the job. >> >> Thanks >> Felix >> >> -- >> 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-use...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > -- > 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-use...@googlegroups.com <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- 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.
