How We Build Code at Netflix

Post by jacques_chester » Thu, Mar 10, 2016, 12:33 AM UTC

onetwotree wrote: post #72

mkobit wrote: post #61

I'm interested in knowing more about the "25 Jenkins masters" that they have, and how much they have modified/built for Jenkins to make it work for them. We are currently in a state of "big ball of plugins and configuration". 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 "do ev…

I think most people do. We did a couple of things to get out of that state at Conjur. First, we made all of our builds into docker containers. Under this system, slaves (we call 'em executors now) only contain very basic software - docker, git, and make to be specific. This means that our builds are entirely self contained, and we don't have to worry about, for example, messing around with RVM on executors. If the co…

Post by palgraham » Thu, Mar 10, 2016, 12:36 AM UTC

pitt1980 wrote: post #58

dang wrote: post #52

Earlier quoted context omitted.

Please stop posting these.

why? I'm trying to keep track of things that catch my eye

Post by seanp2k2 » Thu, Mar 10, 2016, 1:21 AM UTC

Gratsby wrote: post #78

> The Netflix culture of freedom and responsibility empowers engineers to craft solutions using whatever tools they feel are best suited to the task. I absolutely love that. I'm a huge fan of what Hastings and company have done over there in terms of culture and making Netflix a unique and desirable place to work. I think it's time for another round of "find a way to make Netflix hire me."

Post by seanp2k2 » Thu, Mar 10, 2016, 1:28 AM UTC

tracker1 wrote: post #60

jfindley wrote: post #35

Earlier quoted context omitted.

We are doing something very similar (mesos rather than k8s), also in a financial organisation. Our main issue is also security - as docker containers aren't very good at actually containing, from a security PoV, we're using SELinux MLS, assigning each container a unique SELinux level/category (fedora-atomic sets this up nicely for you if anyone wants to try). This is great for security, but breaks so many things - lo…

Along a similar grain, I'm curious if anyone's used Joyent's infrastructure stack internally... I know they offer it, but not familiar enough with it. It seems Solaris containers as a base for docker containers is a better security model, but not sure what parts, if enough is open to implement without paying consultation from Joyent to get started even. It's definitely a compelling model. I am only slightly surprised…

Post by cryowaffle » Thu, Mar 10, 2016, 2:15 AM UTC

hitekker wrote: post #3

mattiemass wrote: post #2

Very cool article. Amazing how much tooling Netflix has built themselves.

I believe at least some parts of the tooling were developed by an embedded team from Pivotal Labs.