CloudBees

“I know it’s a cliché, but the folks at CloudBees have taught me that there’s no such thing as a stupid question. Jenkins can become a tangled mess, especially when plugins aren’t playing well with one another. On such occasions, a silly suggestion can spark the idea that resolves a complex issue.”

“If there’s one word to describe CloudBees’ support team, it is “consistency.” I always get expert and easy-to-understand answers to my questions no matter how trivial they may seem to me.”

“Having CloudBees on board really does help the developers have time to write code, but at the same time, we're starting to see them get excited in the process beyond just their code. They're starting to get involved.”

““When you are building a new relationship, there is always trust that has to be established. What we have consistently heard from CloudBees from the start is ‘How can we help you get better. How can we help drive your business results?”

“Whyde says that CloudBees is “one of the few companies that I’ve worked with that will go above and beyond to make sure you are successful with their product. It’s not just ‘here’s your license and now we’re through.’” Instead, “from the very beginning it’s very much been a high touch, very engaged, strategically focused relationship about how they can help TransUnion improve our engineering practices and drive results within our technology teams.””

““What we always hear from CloudBees is ‘How can we help you get better? How can we help drive your business results?” says Whyde. “And that’s what you want to hear from someone you are working with to improve your engineering practices.””

““One of the delights that we’ve had with CloudBees is the diversity of different paths we’ve been able to take as emerging technologies and capabilities have come forward in our strategy and playbook,” Whyde says. “CloudBees has enabled us to really accelerate toward those things and leverage capabilities that the engineering community is already familiar with and comfortable operating.””

““Working with CloudBees is more than a transaction; it is an actual relationship. That happens because CloudBees is equally invested in our company’s business results and outcomes.””

““What we’ve already seen in terms of increasing developer velocity and the volume of work across our technology footprint, the value from our build-once-deploy-many capabilities over our CI/CD pipelines, and the governance we get from CloudBees CI has been great for TransUnion.””

“Thanks to CloudBees, Tietoevry Banking continues to create innovative and secure products for over 150 financial institutions and banks that serve individual and institutional customers in 12 international markets.”

“CloudBees is helping Tietoevry rein in our Jenkins environment. We have standardized processes, implemented access and source control mechanisms, automated workflows, and increased production capacity. My team spends less time managing our Jenkins environment and our developers output more code faster. The result is shorter development cycles, faster updates, more new products, and quicker reactions to changes in regulatory frameworks and trends in finance and banking.”

“We’re delighted with the quality of the platform and the level of support, and we recently renewed our CloudBees contract for another three years.”

“My team spends less time managing our Jenkins environment and our developers output more code faster.”

“Working with CloudBees Feature Management has been smoother than we could have hoped,” explained Rubin.”

“Our primary requirements were to maximize the speed of development and deployment, so it was critical for us that the solution we choose was engineering friendly,” explained Oren Rubin, CEO at Testim.”

“I want to give a shout out to the CloudBees team. There were times that I was personally stuck and CloudBees was able to guide us to the right path,”

“Today, each developer gets the same Docker image every time they run a build, so developers always get a clean, predictable image. This helps with a lot of issues we were seeing before, where files would buildup in an agent or an agent became out of sync or some files were missing in a library,”

“With CloudBees CI up and running, you almost don’t have to monitor or worry about it. It helps the developers keep doing business as usual despite being remote or despite all the other interruptions they might have,”

“By running CloudBees CI in the cloud, we could move from a monolithic system to one that allows domains to be segregated on different masters, so that changes on one master don’t affect others. You can actually customize each of these masters to their own specific needs,”

“Good developers and good administrators like to add value and do exciting work, so you can’t keep good people around if all they do is maintain 30 or 40 VMs. It’s always our goal to work smart and not just have our people do busy work. Moving from on-premise to the cloud helps us achieve that,”

“Before moving to CloudBees CI on Amazon EKS, we upgraded once in two years. That’s how painful it was in our old system. Now in the new system, we’ve upgraded three times in the last six months, giving our developers the latest plugins, latest changes and latest security features,”

“We used to have four people dedicated to one upgrade over a three-week period. That’s just not scalable and we couldn’t operate that way for long. After migrating to CloudBees CI on Amazon EKS, we can do the same upgrade with one person in just two to three hours. That’s a huge improvement,”

“Switching to CloudBees CI meant we no longer needed to maintain 35 to 40 static Jenkins agents. This has made tremendous sense in terms of time and cost savings,”

“We could not have accomplished this with the open source version of Jenkins alone. CloudBees CI has given us the way forward.”

“Our deploy times have roughly been cut in half, and our ability to deploy hotfixes and recover from incidents has gone down from a factor of (sometimes) hours to minutes.”