Cloudbees, a company formed by JBoss veterans to build and promote a Java-focused PaaS, is getting out of the PaaS business. It is instead refocusing completely on Jenkins, the open-source continuous delivery tool set, according to company CEO Sacha Labourey. In the near term, Cloudbees is working to help a couple hundred PaaS customers migrate their work to alternatives such as Amazon Web Services’ Elastic Beanstalk, Google App Engine and Heroku being the most likely destinations, he said.
For software developers, continuous delivery is a methodology that lets them automate and reiterate so that production-quality code is ready faster.
This news could bolster the contention by skeptics that the market has yet to catch up with PaaS– essentially cloud infrastructure developers can use to build, test and deploy applications. [company]Heroku[/company], now owned by [company]Salesforce.com[/company] is a pioneer here, [company]Microsoft[/company] Azure started out as a PaaS, adding more basic nuts-and-bolts IaaS capabilities last year; Cloud Foundry is an open-source PaaS; and [company]Apprenda[/company] offers a private PaaS for .NET and Java developers.
Labourey acknowledged that PaaS hasn’t hit that “hockey stick growth” he and others had expected, but he still thinks it’s an important market segment. Cloudbees has been doing more Jenkins work of late, and since many Jenkins customers are also PaaSes, there was a conflict and confusion. Concentrating on Jenkins “opens a lot of doors that weren’t open before. Customers would say we like what you do with Jenkins, but what should we do with PaaS?”
Cloudbees also said it will work with Pivotal to make sure its enterprise-class Jenkins will work well with Pivotal’s commercial Cloud Foundry implementation.