As a way to address the many challenges associated with supporting DevOps and adopting Continuous Delivery (CD), CloudBees has released a new Jenkins platform to help teams deliver software.

CloudBees, a company that provides solutions to help DevOps team respond to software delivery business needs, released what it called the CloudBees Jenkins Platform—Private SaaS Edition (PSE). PSE is a turnkey, elastic CD-as-a-Service solution for enterprises, and according to the company, it is the first commercially available Jenkins-based CDaaS. The PSE lets developers deploy on a private cloud quickly, and it shares services across projects.

(Related: Continuous Delivery means getting code where it needs to go)

The new platform provides other cloud-native capabilities, including Docker deployment and Mesos large-scale cluster management, which will allow enterprises to run and manage Jenkins across the enterprise on their own private cloud, or by using dedicated AWS resources.

“More than ever before, organizations need to accelerate software delivery to meet business demands and stay ahead of the competition,” said Sacha Labourey, CEO of CloudBees. “They are moving to Continuous Delivery practices to build, test and deploy high quality software more quickly.”

The platform comes with several features:

  • Cloud-native deployment on Amazon AWS and OpenStack, which allows developers to scale resources for Jenkins-based software pipelines.
  • Instant startup of new projects, which allows teams to get started on new projects immediately with an enterprise Jenkins environment.
  • Automatic failover, which allows developers to spin up new Jenkins resources automatically in the event of an unexpected failure, reducing downtime and automatically detecting and recovering from fault situations without operator intervention. Additionally, configure automated storage backups via NFS/EBS to allow for seamless failover of masters.
  • Increased Jenkins utilization, which allows developers to create Jenkins environments to share across departments and geographies. Shared service teams have one platform to manage, but are able to provide usage models for teams.
  • Developers can share resources across Jenkins deployments, including templates, folders and credentials across clusters to eliminate delays in deploying new Jenkins services.