[Buildbot-devel] Mozilla moving away from buildbot?

[Dustin J. Mitchell]

> To provide an alternative perspective: we at Unity had to make the same
> decision to modernize.  After years of using TeamCity (which was rife with
> performance problems and a lack of the flexibility we needed to deal with
> the complexity of our codebase and the number of builds and developers we
> needed to support), we made the decision to move to what we consider 'a
> custom solution built on top of buildbot' which we call 'Katana'
> (https://github.com/Unity-Technologies/buildbot/tree/katana).  We have spent
> over a year on this (with significant investments especially on the UI side)
> and just recently moved to to it for production use with our main codebase.
> Our developers couldn't be happier . . . and my team (Build & Infrastructure
> Engineering) now has the ability to support our development team in the way
> that has been needed here for a *very* long time.

That's awesome!  That's also exactly how I'd like to think of
Buildbot: a framework for building custom solutions.  We have a lot
(lot!) of work to do to make that easier and more natural, but it's
good to know that the approach has worked for Unity!

Dustin