We have an internal plugin that manages chroots for exactly this scenario. We set up the chroot through a BuildWrapper, and we override the launch method so that each build step enters the chroot before it executes. There’s a lot of internal-only code in here, so it’s not something we can open source. However, if you want more information, I can sketch out some more detail for you.
-- Dean On 2/22/12 2:57 PM , "Mark Waite" <markwa...@yahoo.com> wrote: I experimented once with a "chroot" environment as a way to have different configurations on the same Linux machine. I found chroot to be more complicated than I was ready to use at the time, but I believe it can be used to provide different executable versions hosted over the same Linux kernel. If you need different Linux kernels in addition to different libraries and tools, then I think you'll need separate machines (physical or virtual). Mark Waite From: Les Mikesell <lesmikes...@gmail.com> To: jenkinsci-users <jenkinsci-users@googlegroups.com> Sent: Wednesday, February 22, 2012 1:19 PM Subject: custom build environments? Does anyone have suggestions for how to get Jenkins to make Linux builds that don't match the stock system environment that autoconf/configure would find? For example, if you want to have multiple versions of boost installed and compile jobs that each need some specific version.
