Extending and Scaling Jenkins

Shared visibility and control over islands of automation to improve productivity, predictability and compliance

With 200,000 downloads and counting, Jenkins is everywhere. Easy to set up and customize, Developer teams love it. And because it’s free, each team runs their own. Organizations want to gain centralized visibility and control over the application build process, and eliminate the overhead of having each team maintain their own build system. By simply adding an CloudBees Flow agent on each Jenkins Server, CloudBees can help.

agile usecase infographic

Before CloudBees

  • Every team has their own non-standard non-compliant and standalone flavor of Jenkins and inbuilt build processes.
  • Each team running its own Jenkins build server means there is low utilization and no sharing of expensive hardware resources.
  • Jenkins servers get overloaded with too many jobs, or jobs fail quietly. Jenkins instances fail and root cause information (logging) is lost.

With CloudBees

  • Adding CloudBees Flow allow centralized visibility and reporting into what is being built, by whom. CloudBees Flow provides centralized, secure control of the build environment and allows standardized configuration and best-practice process definitions.
  • CloudBees Flow allows resource pooling to provide scale-out access to keep utilization high and costs low.
  • CloudBees Flow clustering provides horizontal scalability and fault tolerance so jobs always finish and pipelines keep moving. When problems occur, error information is kept for easy process troubleshooting.

Learn how CloudBees Flow enables you to scale and extend Jenkins to gain shared visibility and control over islands of automation to improve productivity, predictability and compliance

Or, contact us to discuss how CloudBees can help you deliver better software, faster and safer.

Learn More