I’m a DevOps Admin for a company that has been using Cloudbees Jenkins. With the new licensing change, I have lingering questions regarding our previous investment in high-availability, operation-center, and update-center. To make matters worse, I spilled my instant cappuccino on my keyboard today because I was so distracted by the changes to Cloudbees Jenkins (the caffeine low is doing nothing to calm my frayed nerves). After stellar customer service, I’m worried about how this will translate in the future. I have some very basic questions that I haven’t been able to get answered and this is going to make it very difficult to rationalize pricing. I want to bring this to my CFO, but first I need answers to some of my questions. In order to continue with what we currently have installed, do we need to buy Team or Enterprise versions of Cloudbees Jenkins?
Frayed DevOps Man
Dear Frayed DevOps Man,
I’m sorry to hear about your instant cappuccino and keyboard. Try some dry rice to saturate the liquid out of your keyboard. Your Cloudbees Jenkins issues are a bit more complicated, but I’ll do my best to help you piece everything together. I had the opportunity to speak with Yu-Chen Hsueh (Chen), who is a Sr. Solutions Architect at Cloudbees, and he had some solid insights that speak to your questions.
Let me start by assuring you that Cloudbees Jenkins Team and Cloudbees Jenkins Enterprise will both come with the stellar service and vetted upgrades that you’ve grown accustomed to via the BeeKeeper Assistant. Cloudbees Jenkins Team is a single master or multiple masters (with no operations center) based on the number of users accessing each master. Chen says, “Cloudbees Jenkins Team is just the open source Jenkins core we all know and love. It’s distributed as a jenkins.war file, a Dockerfile, an AWS AMI, etc. It can be thought of as OSS Jenkins + QA testing by CloudBees + CloudBees Assurance Program validated plugins from CloudBees + support by Jenkins experts.”
In order to get high-availability and operations-center, Cloudbees Jenkins Enterprise will be your best option. “CloudBees Jenkins Enterprise deploys an entire Jenkins cluster, this is designed for shared services teams who need to provide Jenkins as a service or CD as a service. A bigger offering to be sure, but designed with extremely elastic capacity and built-in fault tolerance. For instance, all build slaves are ephemeral by default, and if a Jenkins master goes down for whatever reason the CloudBees Jenkins Enterprise product will automatically failover running job from that master to a replacement”, Chen says. Current cloud vendors supported by Cloudbees Jenkins Enterprise are AWS (Amazon Web Services) and OpenStack. There are other cloud providers (both public and private) that are being worked on.
In short, it appears that Cloudbees Jenkins Enterprise would be the best fit for you. You may still have lingering questions, but this should help you make your decision, and, perhaps more importantly, convince your CFO that it’s worth the expense…as soon as Cloudbees releases the pricing.
Dave (from IT)
Have a question for Dave? We welcome your questions, comments, concerns! For additional information, feel free to reach out to Dave at David@Opensourcearchitect.co or visit our website opensource.io
To stay in the loop on training courses, updates, or industry news, follow us on Twitter, LinkedIn, or give us a ‘Like’ on Facebook!