How We Build Code at Netflix
I&#x27;m interested in knowing more about the &quot;25 Jenkins masters&quot; that they have, and how much they have modified&#x2F;built for Jenkins to make it work for them.<p>We are currently in a state of &quot;big ball of plugins and configuration&quot;. A bunch of plugins have been installed, and lots of manual configuration has been put into jobs so that everybody has what they need to build their software. It has led to Jenkins being a &quot;do everything&quot; workflow system. The easy path that Jenkins provides, to me, seems like the wrong one - it makes it easy to just stuff everything in there because it &quot;can&quot; do it. This seems to leads to tons of copy&#x2F;paste, drift, all types of different work being represented, and it is starting to become unmanageable.<p>Have others seen this happen when using Jenkins? How have you dealt with it?