New York Times Delivers a Continuous Integration Pipeline with Docker


The New York Times Company is a media organization focused on creating, collecting and distributing news and information. The Company includes newspapers, digital businesses and investments in paper mills. Its content reaches its audience through its print products, online and through other digital media, including smartphone, tablet and e­-reader applications.


New York Times Interactive News Department (IND) consists of technologists that are also journalists, including designers, developers, and reporters. They needed to enable every member of the IND team to keep things online, requiring a reliable path to production and the ability to manage their own code. Moving from Intail to Chef with a Ruby stack they believed could automate enough of the components of Chef to give their journalists a self service tool to deploy applications themselves, scale up a cluster, changing their routing, etc. but ran into challenges with their production environment. The process was slow, complicated to get up and running, checking all scripts from the beginning of time and preventing them from delivering a continuous integration pipeline. They required a new a solution that they could host themselves so they adopted Drone, a Docker based CI system.


When the IND team looked at the underlying components of Drone they discovered the value of Docker. The Docker components had turned what was previously a super onerous provisioning step into a build step, providing a truer sense of versioning. Chef had given them a way to description their infrastructure code but that code was still subject to runtime quarks and if anything went wrong they had to run them again. Docker was able to give them true versioning of the system, when files were modified in the system every change was captured by Docker, not just the ones that were addressed. To keep up with the speed of news the IND team run almost entirely on AWS giving them the ability to scale up 20­30 more servers based on the news cycles. Docker’s portability allowed them to easily run on AWS solving their density and speed challenges and delivering a continuous integration pipeline. The IND team is now able to manage their own code, at the speed of news, with the control they require.

Get Started for Free
  • Having the right kinds of controls to make sure that changes to production are going through the right processes to make – and getting audited appropriately is important for us. So, the role-based access control is really good.

    Eric Westfall, Enterprise Software Architect, Indiana University
  • We realized that our vision and what we wanted to achieve long term in terms of the datacenter modernization and what was required in our architectural blueprint, that fit very well with what Docker was providing.

    Ajay Dankar, Senior Director Product Management, PayPal
  • Docker’s CaaS approach will enable us to drive transformation across the entire application life cycle from development to operations. A key feature for us is the end-to-end integration with Docker Content Trust to centrally administer and control our images so that only signed and validated content can be used or deployed into a production environment. With Docker, we will be able to ensure application portability, whether it is between dev and ops or between the datacenter and the cloud.

    Keith Fulton, Chief Technology Officer at ADP