On Tue, Jan 12, 2016 at 12:25 PM, Mike Percy <[email protected]> wrote:

> On Mon, Jan 11, 2016 at 1:02 AM, Todd Lipcon <[email protected]> wrote:
>
> > I spent some time this weekend working on setting upstream Jenkins so we
> > can move from the Cloudera-internal precommit builds to something visible
> > to all developers.
>
>
> > At the same time, I've been working on switching us over to fully
> > distributed test running.
>
>
> Todd this is really good for everyone and I'm really looking fwd to having
> this up and running!
>
> The most controversial one is changing RELEASE
> > precommit builds to use dynamic linking -- otherwise the test binaries
> take
> > 20GB of space and take forever to distribute to the tester slaves.
> >
>
> We could make this less controversial by having Jenkins kick off a nightly
> statically linked RELEASE build using "normal" local ctest, just to make
> sure we don't miss something that only triggers for that setup.
>

Yea, good idea. I also think that eventually we'll want some tests running
against deployed clusters, which would of course be "production" builds
(static-linked release). But that's probably many months off - walk before
we run :)

-Todd

-- 
Todd Lipcon
Software Engineer, Cloudera

Reply via email to