FAQ for Customers of RUN@cloud

On September 11, we announced we will no longer offer RUN@cloud to new subscribers. Existing customers will not be able to use it as of December 31, 2014. On this page, we have pulled together the most frequently asked questions to provide additional information for CloudBees RUN@cloud customers.

1. I use CloudBees in various ways. What exactly is impacted by this decision?

2. I’m trying to sort out my options. How can I get help?

3. How will my billing change, and how will that be handled as I transition to another runtime service?

4. Where can I find specifics about migrating to other services?

5. How long do I have to deal with the changes I need to make?

6. What happens to Ecosystem Partner services I’m using?

7. I have been using CloudBees for free. Can I still do that?

8. I’m doing Continuous Delivery, deploying to RUN@cloud. How does that work in a world without RUN@cloud?

9. Are there any other implications to CloudBees’ business beyond RUN@cloud?

10. How does your focus on Jenkins relate to your involvement in the open source community?

11. It seems like there is a lot of churn in the PaaS runtime space. What’s going on, and how should I consider that when I look at my options?

12. I see you announced a partnership with Pivotal Cloud Foundry. How does that relate to the news about your Jenkins focus and shutting down RUN@cloud?

1. I use CloudBees in various ways. What exactly is impacted by this decision?

Only your RUN@cloud hosted applications and database offerings are impacted by this decision. New customers will not be able to sign up for RUN@cloud services. Existing paid customers will have until December 31, 2014 to transition to another provider.

2. I’m trying to sort out my options. How can I get help?

First, you should check out the migration documentation we put together. If it doesn’t answer your questions, send an email to help-run@cloudbees.com​ or file a support ticket. We will be providing hands-on help for customers to transition to other providers until the end of October.

3. How will my billing change, and how will that be handled as I transition to another runtime service?
Many customers use CloudBees purely on a “transactional” basis, billing against their credit card monthly. When you cancel a service, we ensure the billing is properly reconciled, both for our services and for Integrated Partner services. For customers with yearly agreements or prepays, please contact us on help-run@cloudbees.com​​ or through our support portal to make sure the accounting is properly handled. In any case, if you have any specific concerns or issues related to billing, contact us on help-run@cloudbees.com​​ or through our support portal.

4. Where can I find specifics about migrating to other services?
The migration doc is the place to look. We intend to improve this document as we learn more during the process.

5. How long do I have to deal with the changes I need to make?
The RUN@cloud hosted application and database services will be running until December 31, 2014. However, we want to encourage customers to get a jump on the process, which is why we’re offering transition assistance until the end of October. If you have some special circumstances that make this timing particularly problematic, please contact us at help-run@cloudbees.com​​ so we can address it with you.

6. What happens to Ecosystem Partner services I’m using?
We have two categories of technology partners: Integrated Partners and Verified Partners. Integrated Partner services are accessed through and billed to you by CloudBees. Verified Partner services work with CloudBees, but there is no identity or billing integration.

We have contacted all Integrated Partners offering services for RUN@cloud apps and databases. Our joint goal is to ensure your usage of the partner service can go on in an uninterrupted manner. In many cases this just involves opening an account directly with the partner and filing a support ticket with them, providing the details of your service usage on CloudBees. Details for each partner service are covered in the migration document.

For Integrated Partners with services that apply to DEV@cloud, there is no impact.

We refer to the last category of technology partners as Verified Partners. If you’re using one of these partner services, you are already doing so through an account you set up with that partner. Your use of some of these services may be more related to an app you have running on RUN@cloud, in which case you can continue to use that partner service with another IaaS or PaaS service, just as you do with CloudBees. Development-time services from Verified Partners would not be affected.

7. I have been using CloudBees for free. Can I still do that?
As part of our focus on Jenkins and the shut-down of RUN@cloud, we are moving to a pure trial-based model and eliminating our Free tier plan. Effective immediately, new customers will have access to a two week free trial plan, but there will be no Free plan available as we have offered in the past. We will be transitioning existing Free plan users to a trial basis as of September 24, 2014. That free trial will expire on October 10, 2014. This gives existing free users 30 days from our announcement to move to a paid plan on CloudBees or to transition to another service provider.

Note that our FOSS program - providing free services to qualified FOSS projects - remains in place and is not affected.

8. I’m doing Continuous Delivery, deploying to RUN@cloud. How does that work in a world without RUN@cloud?
It works quite well, actually! We already support deployments from DEV@cloud to other PaaS providers like AWS, Elastic Beanstalk, CloudFoundry.com and Google App Engine. Our focus on Jenkins will allow us to improve and expand these facilities to make them even easier and more seamless in the future. If you have specific questions around the stack you’re using and the process you have in place, please contact us at help-run@cloudbees.com​​.

9. Are there any other implications to CloudBees’ business beyond RUN@cloud?
No, beyond our ability to apply more cycles to Jenkins and our offerings on-prem and in the cloud. Jenkins is really an incredible phenomenon, with adoption growing rapidly both for developers and operations people. This growth in Jenkins has fueled our business growth, and our increased focus on Jenkins will drive more business and growth for CloudBees.

10. How does your focus on Jenkins relate to your involvement in the open source community?
We are deeply committed to the success of Jenkins as an open source project, from our CTO (you may have heard of him) on down. We’re also very proud of the way we have built a business that succeeds when that open source project succeeds and which adds value to the community and Jenkins users. We’re going to continue our strong investment and engagement with the Jenkins community, and this move will only help us to do that.

11. It seems like there is a lot of churn in the PaaS runtime space. What’s going on, and how should I consider that when I look at my options?
Yes, as they say on Facebook, it’s complicated. The PaaS runtime marketplace is really dynamic, with some very large, strong players. We wrote up some of our thoughts on the topic and published them on the CloudBees blog.

12. I see you announced a partnership with Pivotal Cloud Foundry. How does that relate to the news about your Jenkins focus and shutting down RUN@cloud?
The partnership is a great example of how focusing on being the Enterprise Jenkins company opens new doors. We already worked with Pivotal, Google and Amazon to make deployment to their environments simple. But with Pivotal’s strong focus on bringing continuous delivery of a new generation of apps to the enterprise, combining together to help deliver that solution just made sense. As more and more companies step up to Continuous Delivery, they’re looking to Jenkins as the hub to orchestrate the delivery across and ops. You should expect to see us engage with other partners to help drive the role of Jenkins and Continuous Delivery with them.