[LLVMdev] Plans for the Apple supported Darwin buildbot cluster

Chris Matthews
Tue, 12 Aug 2014 22:33:03 -0000

It was mostly pragmatic concerns that made us want to switch.

We are using both Jenkins and Buildbot internally.  We found more people had
Jenkins experience than Buildbot.  We wrote custom code for a lot of features
buildbot was missing, that seem to come standard in Jenkins.  Our extensions to
buildbot internally were getting out of control, and sucking up a lot of
maintenance time.

As a project, Jenkins seems to be moving faster. Jenkins also makes it very easy
to setup new jobs, no checking out zorg repos!

We have a selection of plugins which make some of these problems you mentioned
go away.  We are using the failure cause management plugin to extract errors
from logs, and the email-ext plugin make nicer emails.  One thing we have been
working towards is isolating infrastructure failures (svn, disk space etc) from
build and test failures.

We have not found one to be ‘more’ reliable than the other.

> On Aug 12, 2014, at 1:49 PM, Renato Golin <renato.golin at
linaro.org> wrote:
>
> On 12 August 2014 19:34, Chris Matthews <chris.matthews at apple.com>
wrote:
>> The most notable change will be a switch from Buildbot to Jenkins.  We
will
>> be replacing the current phased system with a Jenkins analog and
reproducing
>> the current builds.  The Jenkins will execute scripts for each
“project”
>> that we will be checked in to zorg.
>
> Hi Chris,
>
> I'm very interested in this. Can you share some of the decisions on
> moving to Jenkins?
>
> I ask that because we have our GCC testing on Jenkins and LLVM testing
> on Buildbots, and to be honest, buildbots are more stable and
> reliable, not to mention having more readable web pages, error
> messages and emailing committers, etc. Can Jenkins (at least in your
> setup) do the same?
>
> I really don't care much how I run the tests, as long as they keep me
> informed and don't hassle me, which has been an almost free ride with
> the buildbots so far.
>
> If you guys add Jenking support I may also have a go here internally,
> and if you guys could also share the Jenkins configuration, I could
> update our own copy with a decent setup. :D
>
> cheers,
> --renato