Post image

CloudBees Build Acceleration Helps Force10 Save at Least 200 Engineer-hours Per Week

Case Studies

Shining a spotlight on CloudBees customers who Build Stuff that Matters.

All Case Studies


Force10’s builds had increased to over three hours and previous attempts to address the problem had not yielded the desired results. Force10’s first attempt was to invest heavily in hardware by providing a dedicated dual CPU build machine for every two developers. This was not scalable, and the problem remained as their software build continued to grow, quickly becoming unacceptably long. Many builds could not successfully utilize GNU Make –j and the benefits were minimal. One build went from 51 minutes before –j to just 43 minutes which wasn’t much of an improvement.

"In this business, slow execution can mean missing an entire product cycle, which can cost the company tens of millions of dollars and competitive leadership. Everyone, including our CEO, recognized that improving build speed was key to getting our products out on time."

Arun Viswanathan
VP of Software Engineering


  • Significant cost reductions. CloudBees CloudBees Build Acceleration helped Force10 improve engineering efficiency and speed up new releases to market with an estimated savings of at least 200 engineer-hours per week. Build times are no longer a concern.

  • Process automation. CloudBees Accelerator automatically recognizes and corrects missing dependencies, builds no longer break and manual Make file maintenance is a thing of the past.

  • Substantial productivity improvement. The developers and build masters at Force10 use the CloudBees Accelerator cluster, and the company’s three hour build times have been cut by over 80.

  • ​​​​​Seamless and scalable. This scalable solution allows Force10 to easily add more servers to the cluster and continue to speed up builds as their code base grows.