<story><title>How We Build Code at Netflix</title><url>http://techblog.netflix.com/2016/03/how-we-build-code-at-netflix.html</url></story><parent_chain></parent_chain><comment><author>mkobit</author><text>I&amp;#x27;m interested in knowing more about the &amp;quot;25 Jenkins masters&amp;quot; that they have, and how much they have modified&amp;#x2F;built for Jenkins to make it work for them.&lt;p&gt;We are currently in a state of &amp;quot;big ball of plugins and configuration&amp;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 &amp;quot;do everything&amp;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 &amp;quot;can&amp;quot; do it. This seems to leads to tons of copy&amp;#x2F;paste, drift, all types of different work being represented, and it is starting to become unmanageable.&lt;p&gt;Have others seen this happen when using Jenkins? How have you dealt with it?</text></comment>
<story><title>How We Build Code at Netflix</title><url>http://techblog.netflix.com/2016/03/how-we-build-code-at-netflix.html</url></story><parent_chain></parent_chain><comment><author>vlucas</author><text>For those wondering about how this applies to Node.js use a Netflix like myself, it&amp;#x27;s in there towards the bottom of the article:&lt;p&gt;&amp;gt; &amp;quot;As Netflix grows and evolves, there is an increasing demand for our build and deploy toolset to provide first-class support for non-JVM languages, like JavaScript&amp;#x2F;Node.js, Python, Ruby and Go. Our current recommendation for non-JVM applications is to use the Nebula ospackage plugin to produce a Debian package for baking, leaving the build and test pieces to the engineers and the platform’s preferred tooling. While this solves the needs of teams today, we are expanding our tools to be language agnostic.&amp;quot;</text></comment>