Another possibility would be to put Boost in a non-standard location where 
autoconf/configure would never find it, install various versions of Boost that 
you need into various directories, and then pass command-line arguments to 
autoconf/configure specifying where to get your Boost library from.

A third one would be not to install Boost on your build host at all, but to 
throw the various versions into source control (or artifact repository) and 
pull them out at compile time as needed.

--Rob Mandeville
Litle & Co.
www.litle.com

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Dean Yu
Sent: Wednesday, February 22, 2012 8:05 PM
To: jenkinsci-users@googlegroups.com; Mark Waite
Subject: Re: custom build environments?

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.

The information in this message is for the intended recipient(s) only and may 
be the proprietary and/or confidential property of Litle & Co., LLC, and thus 
protected from disclosure. If you are not the intended recipient(s), or an 
employee or agent responsible for delivering this message to the intended 
recipient, you are hereby notified that any use, dissemination, distribution or 
copying of this communication is prohibited. If you have received this 
communication in error, please notify Litle & Co. immediately by replying to 
this message and then promptly deleting it and your reply permanently from your 
computer.

Reply via email to