The lines are blurring in the Platform-as-a-Service world. It used to be that if you developed in a given PaaS, you probably deployed in that PaaS. But that’s changing. For example, CloudBees, the self-proclaimed Java-specific PaaS will now let developers that build applications on its DEV@cloud to deploy their work on Cloud Foundry, as well as on its own platform.
The goal is to make it easy for developers to develop what they want using CloudBees — taking advantage of its Jenkins-based continuous integration capabilities — to deploy what they build where they want.
CloudBees CEO Sacha Labourey said his company focuses on the whole application life cycle, not just development, not just deployment. In October, the company announced a similar deal that lets its users deploy on Google App Engine.
“If you’re a GAE user you can subscribe to our services… it’ s not that we’re moving to Cloud Foundry as a company, it’s just that customers have freedom of choice. If you prefer GAE or Cloud Foundry to us for deployment, that’s fine,” he said.
CloudBees users wanting to deploy to Cloud foundry can sign up here.
Here’s the thing about PaaS: Many developers love them because of the freedom and flexibility they offer when it comes to actual development. Moves like this one mean that deployment options for their finished code (if there is such a thing) are opening up as well.