News for hackers. Stuff that matters.

A comment on How We Build Code at Netflix. Parent comment

Re:How We Build Code at Netflix by sytse on Wednesday March 09, 2016 @02:29PM (#11255158)
I think the copy/paste is not inherently bad as long as it is version controlled and visible to everyone, that is why we have all CI configuration in the repo with gitlab-ci.yml

I was surprised about needing 25 different masters. On GitLab.com we have a single clustered application that handles over 1600 GitLab Runners (called build slaves in Jenkins).

[ Parent | on HN ]
Re:How We Build Code at Netflix by onetwotree on Wednesday March 09, 2016 @02:33PM (#11255187)
Agreed, we have a basically arbitrary number of runners (near releases it gets into the hundreds), and one master handles it just fine.
[ Parent | on HN ]
Re:How We Build Code at Netflix by sytse on Wednesday March 09, 2016 @03:32PM (#11255536)
Glad to hear that. We'll soon announce an autoscaling runner that allows you to boot up new instances automatically. I love that you sometimes run hundreds of runners, would you like to do a guest post? Email me at [email protected]
[ Parent | on HN ]