On Tue, Jan 17, 2017 at 9:39 AM, Marshall Schor <[email protected]> wrote: > Hi, > > We have part of our project that is in C++. We're looking into a Jenkins job > for CI for it. > > It requires as prerequisites: Apache APR, ICU, Xerces, and maybe some other > somewhat standard components. > > When building on private machines, the technique is to obtain these by either > installing prebuilt versions, or first "building" these, more or less as a one > time operation (repeated sometimes when toolchain levels change). > > What's the best practice on Apache Jenkins? Are there a group of machines > where > somewhat standard packages like the above are installed (at various versions)? > If so, is there a standard naming of these to find them? If not, should each > build do its own build of these components, every time the build runs?
Personally, I've recommended and used Docker containers as a way to capture the build environment to a great deal of success. The bonus points is that it also gives a 100% reproducible build environment to your community. Which means no longer having "but it builds on my machine!" arguments. Thanks, Roman.
