The document discusses scaling Jenkins, an open source automation server. It notes that over 83% of users consider Jenkins mission critical. Scaling Jenkins involves increasing the number of slaves, jobs, builds and concurrent HTTP requests. It also involves deciding between a single or multiple masters. The document outlines factors to consider when managing Jenkins at large scale like security, plugins, resource utilization and high availability. It presents a reference architecture with multiple Jenkins masters, load balancers, shared build nodes, and centralized management and access controls.