CloudBees

“It was a tough time for us, but CloudBees really helped us through it. CloudBees CI has an intuitive way of managing Jenkins, and helped us get our processes streamlined and efficient.”

“Automating provisioning with CloudBees CI is a game-changer. What used to take developers a few days now only takes 10 minutes to complete.”

“This new portal, with all its new functionality, was like jumping from a bike into a nice car: developers can get where they’re going much faster and more comfortably.”

“We meet with CloudBees weekly and the team will pull in developers or key support staff when we need it,”

“The move to CloudBees CI shaved at least 30 minutes off our testing times,”

“With CloudBees CI, instead of taking as long as three days to get a code change into our development systems, we are doing it in a couple of hours,”

“That lets me know that CloudBees CI is making our developers happier by making their jobs easier and giving them more time to create new capabilities for clients instead of worrying how to deploy and test those capabilities.”

“We’ve had positive feedback from our developers,”

“We use the Role-Based Access Control plugin because we need to customize and ensure that everyone has the appropriate level of access,”

“Jenkins Pipeline has been a huge advantage for us for maintainability, traceability and merging,”

“Moving to CloudBees CI simplified the entire infrastructure and reduced our resource needs,”

“When a company begins offering its software as a service, it increases the expectation to deliver new capabilities faster. We wanted to reduce our cycle times even more,”

“Now, instead of taking as long as three days to complete that process, we are doing it in a couple of hours,”

“We use support frequently, and it has helped us be more efficient, deliver higher quality and enables us to focus on the high-value tasks that really make a difference for our clients.”

“CloudBees CI has become the heartbeat of our development team and the central point that everyone uses to see the status of the code base and what is happening with it right now. Having that transparency and visibility into the quality of our code is incredibly valuable.”

“We can do more in less time and reduce the disruptions in our continuous delivery workflows by reducing the wait times for our builds.”

“CloudBees will release a new revision right away and can push it out to all our clusters immediately. You can't beat that level of service, and it's reassuring to know that we'll never stall because our build acceleration tool is at fault.”

“We reduced build times from roughly eight hours to 90 minutes or less. Instead of waiting an entire day, our developers can go back to their code in a couple of hours, which is excellent for keeping them focused on their work.”

“We felt that CloudBees gave us that centralized oversight, that way of working, that single point of entry, if you like, into how we deliver Jenkins as a service out to our business.”

“We have modernized our DevOps environment and supercharged our CI/CD pipelines in a fraction of the time it would have taken using an open source solution, and we have leapfrogged a few steps along the way.”

“Every change to this codebase required a 25-minute build on Jenkins but was ready in just four minutes with CloudBees CI.”

“CloudBees provided all the capabilities we needed without having to build them ourselves. Given the complexity of engineering required for an organization as large as Markel, this was a huge weight lifted from our shoulders.”

“It took me a couple of days to implement it across the team,” says Le. "It took anywhere from a few hours to one week to implement. Wrapping a feature and getting it out the door is becoming second nature to the team.”

“our developers and the engineers can control and wrap our code in a very safe way that doesn’t impact the functionality of our current production code, and then release it without any impact to the end user,”

“I’ve really leaned heavily on feature flags in order to help time the delivery and release of our student apps,” says Eckert. "The key difference is we don’t have to plan six months ahead of time. We don’t have to be sure this is the exact feature that we want. We can slowly make it into the feature that our users want.”