Name: Velocity Engineered: How CloudBees CI + Unify Drive Faster Delivery
Uploaded: 2025-09-25T10:17:09.129Z
Duration: 1 h 8 s
Description: Velocity Engineered: How CloudBees CI + Unify Drive Faster Delivery

Transcript for "Velocity Engineered: How CloudBees CI + Unify Drive Faster Delivery": Hi, everyone. Welcome to our webinar, Velocity Engineered, How Cloud VCI and Unify Drive Faster Delivery. I'm your host, Liz Bryan, senior product marketing manager here at Cloud Viece, and I'm joined today by Sunil Movadia, our global field CTO. Hi, Sunil. Hey, Liz. Thanks for having me on this. I appreciate it. Great to be here. Thank you. Yeah. Yeah. Let's get started. So on today's agenda, we're gonna talk about the reality and challenges of faster delivery and software development. We all know them well, but worth bringing them up here. We're gonna discuss a real world scenario of many of our customers where we have people that are trying to reduce friction in their life cycle, but they're also trying to get visibility and scale at the same time. And and those things can often work against each other, and and how we can work to resolve that. And then we'll walk through a live demo of the CloudVise Unified product with Sunil. So starting off with the challenges. Modern software teams are under pressure to deliver faster than ever, innovate continuously, and reduce time to value. But chasing this speed without coordination leads to fragility, sprawl, and burnout for your developers. Right? This is this is not news. We all know this. But velocity tends to collapse under invisible complexity, meaning there's a lot going on under the surface that we're not even considering. Platform and engineering teams face a growing set of friction points, including duplicated tools, ungoverned pipelines, inefficient feedback loops, and insecure workflows among many others. These silent problems accumulate, and they drag down productivity, quality, and trust over time. So I'm gonna hop into a real world scenario that we hear from many of our customers. This is Alex, a director of platform engineering. She's struggling a little bit because her organization is growing fast. There's mounting pressure for her to scale, and she's trying to bring new development teams on who have their own processes and their own tools. And she she wants to be open to their processes and tools because developers have their preferences. Right? But then that causes a lot of siloed issues and fragmented systems across the globe. And they could have anything from Jenkins to GitLab to GitHub, and it all doesn't communicate together well. It's a plethora of custom built pipelines. Alice's initial openness has quickly led to chaos. And imagine this, Monday morning, Alex opens up her laptop. She sees a bunch of urgent messages from her developers, including pipeline build fails, security is holding up my deployment, the sprawl is killing us. She hears these issues all the time, but she doesn't have a quick way to look at all these issues, gain visibility, and address them quickly. It is it is such a it's such an old problem, Liz, just to add to that. Right? One aspect of this is that, most of these issues are never surfaced until it becomes a huge problem, right, for production. So, it's such a such a such an issue. Go ahead. Yeah. Yeah. And back to that, I mean, if you think about our iceberg slide, right, that invisible complexity, we don't get to see a lot of that day to day struggle. And and here, Alex's developers are being really vocal, but often, they're not. Right? They're kinda just Yeah. And and it's actually related. It's related to that iceberg issue if you think about it. Right? Because what you're seeing at the very top, of that iceberg, there's so much more complexity and, you know, issues, technical debt under the surface that is causing these issues for Alex. Right? And that's never really surfaced until it blows up to become a huge production issue. Right. And I think everyone can relate when you open up your laptop on a Monday morning and you just see hundreds of Slack messages, and they're all urgent, and you you have a moment of panic. Right? You're like, how do I how do I even begin today? Yes. Yes. With you. So I I feel feel her pain, feel our customer's pain when they come to us with these problems. No doubt. Let's talk about this tools for a minute. Right? Velocity without visibility, it means risk. It means rework and roadblocks, especially when you have tons of tools that don't talk to each other. Mhmm. So, you know, before, if you looked at how Jenkins, for example, people would install Jenkins controllers. Jenkins open source, by the way. They would install Jenkins open source controllers across their entire teams and and and enterprises. Right? And this caused that followed tool effect. Right? And so there's always issues with compliance and bottlenecks. And then the this level of complexity with other tools. So if you're for example, today, a large organization and you have, multiple CI tools, you know, you want that flexibility for one because the developers like to use the tools they like to use. Right? They are, technically, the mechanics of their cars, and so they use what they use. So you can't really restrict that. Right. But the problem there becomes, how do you actually connect these these these tools together so you can get visibility across, the entire, SDLC. Right? And so this is where, something like, you know, like Unified CI, it brings that visibility with with policy as code or, you know, pipelines as code, frictionless government, etcetera. Right? Right. Right. So so this is how, like, platform teams now become accountable for delivery uptime. Right? Because now they have a full visibility and stability across the entire sales. This is really what we call engineering velocity at scale. Right? Mhmm. And you add the layer of security and compliance, just improves that go to market aspect, for for a for an organization. Right. Instead of a lot of isolated islands, you start actually communicating with each other, and you actually start working together across a bunch of teams. And, hopefully, people can still use the tools that they love, but in a more streamlined, standardized manner so that everybody wins. Yep. Right? Deliver faster. They deliver to their customers who stay loyal. Everyone stays happy. And then I'd be alone. Absolutely. Absolutely. Like, you know, if if I use the analogy of, you know, driving a car, you wanna drive the car, you drive every day, and you love it. You, you know, you're comfortable with it. And it takes you from point a to point b, you know, safely, reliably, and that's what you want. Right? So, essentially, it's the same thing for developers today. You know, they want to use the tools they wanna use, but provide that layer of feedback into the end into the enterprise. Right. I don't know about you, but I don't want my car to break down. It's a pain. Right? Hey. You know? So that is always such an issue. Right? But I think I I think in in in the software development world, it is essentially the same analogy, right, if you think about it. Things do break. Right? Yeah. So Okay. Yeah. Yeah. Yeah. Yeah. And back to Alex, I mean, I think we're bringing up a lot of her pain. Right? She wants to scale. Developers wanna keep their tools. They want the freedom to choose. But that causes a lot of friction, a lot of chaos. She she can't get access to everything that she needs. We're we're creating this world that's an ideal space, but Alex isn't living in that today. Right? She's just living in lots of urgent Slack messages, pressure from her leadership, pressure from her developers. It's a it's a tough place to be when you're a a platform engineer or or someone that's in charge of a major team and and you're just trying to deliver what customers want. Yeah. I I agree completely. Right? So, one of the the biggest reasons, managers and, you know, engineering managers, pull their hair out and they become like me, bald. No. It was great. It was great to say that. But the issue there is that, you know, one, they don't have that level of freedom to be able to analyze issues immediately. Right. Right? So they lack that layer of that we call it the control plane, you know, in our lingo. It's that sort of pain of bastion, and and I don't like that term either, but it is what it is. But that layer of visibility Yeah. Yes. Exactly. Right? So that layer of visibility, which which Alex does not have right now in this particular scenario, is what she is direly looking for. Right. Right. It brings some relevance. Yeah. You you know, bring some relevance to the chaos. Yeah. You know? So so her pain is being felt not only by her, but by the people that work for her, by her management. Right? And so the big question is how do we reduce that, you know, level of, that level of pain that Alex is going through? Yeah. Yeah. Absolutely. And and we've already been talking about it. Right? Visibility is essential here, but so is Alex's ability to scale. And if you don't have the systems in place to properly scale with demand, then you can't achieve velocity. It's just not possible. Right? You need capability beyond a patchwork of siloed tools and systems. You need something that's more enterprise capable. Correct. It needs to be able to grow with the enterprise. It needs to be able to address your current team challenges, right, and address also the enterprise needs to grow at scale. Yep. Absolutely. Because we all want more business. Right? Of course. Hey. At the end of the day, you know, what does this boil down to? It's how much money can a company make, right, with a smoother transition to go to market with features that they can provide to their customers re without having to deal with this issue of, you know, the technical debt that comes with, you know, so many tools which is full of friction and slowdowns. Right? A product like probably is Unified brings that observability and governance and metrics together. Right? Now if you have tools like GitHub, GitLab, Jenkins Open Source, Cloudy CI, Circle CI, and then, you know, name a slew of other DevOps tools like Artifactory, SonarQube. Put all these together. Imagine the amount of orchestration that you would have to do. Right? Right. Now imagine you can do it with a product like Cloudways Unify and be able to orchestrate without logging in or slowing down. Right? That's the essence of passive delivery, if you if you look at it purely from an automation and visibility and resilience perspective. Yeah. And we're I mean, we're talking about all the different tools. Right? And we when we think about the SDLC, we want it to look like this. Right? Or we want it to look like the people in the loop that's so popular in software development. Right? Yeah. It's a seamless flow from code to build to test and deploy, and it it looks really nice on paper. But the reality is it looks more like this. Right? And this is just one pipeline. It it's cold. Pipeline. Yeah. And you know the reality. Exactly. And the reality is that these pipelines get embedded, you know, they're parallelized, they're sequenced. Right. They crossover into other pipe like, there's so much complexity, that even this pipeline looks simple, if you think about it. Right? So when you talk about legacy applications, for example, that, you know, companies can't get away from, some of those pipelines I haven't seen, they cause a headache, literally. Worse. Yeah. And, well, and what's the complexity of it all? Right? We can't avoid complexity. Complexity is part of the day job. But when you have complexity that's untracked and you can't get visibility into all of these little bits and pieces, these tools and processes, there's Yeah. Malicious actors out there. Right? People are constantly trying to attack software. They're and and not even only that, it's vulnerability slipping through. Vulnerabilities get exposed every single day. And if you're using old code, which everyone is, literally everyone Yes. You don't know where where the vulnerability lies half the time, and you spend half the day That's inside the vulnerability. Right? That is that is fundamentally one of the biggest issues that, software development has tried to solve. Right? The issue of third party library reuse. So, essentially, these are libraries that you've taken off of the Internet. Right? They're usable great libraries to do the stuff you wanna do. But the fact is that a lot of these come from actors that are unknown. Mhmm. Mhmm. Right? And so you bring them into your code base, and now you're you're pretty much exposed. So you have to be very careful, when ingesting those third party libraries. Right? And be able to actually analyze them, quickly, efficiently. Right. And if if you're thinking of all of the different layers and layers of code that you bring in, how do you find that one issue? You know, your your bill fails and you see there's an issue, but you don't know where it is. And that can be Finding it quickly. Yeah. Finding it quickly. That's the biggest problem. You know? Right. And more than likely, the developer that's looking for the issue that detected it didn't write the original code, doesn't have any context, Has to go find it wherever it lives and then sort it out. Right? With and it probably involves other parties. They can't just do it by themselves. It's a mess. Right. Absolutely. Absolutely. Yeah. So we've talked a lot about the pain. Right? But we have also talked about the Nirvana state. What if you could bring everything together under a unified control plane? Not a rip and replace, not making everybody retire their favorite tools and forcing them into another platform, but just using what you have and making it better. Right? And and getting everything under one single I always think of it as just a tab on your web browser. Right? You can look at everything in one screen. And and that includes the vulnerabilities we were just talking about, workflows, run time, all of the things that you need to monitor on a daily basis to make sure that you don't run into those those regular pains that the software development life cycle experiences. Absolutely. I mean, that the the idea of having a single place to go look at it. Right? The other layer of complexity might be, hey. You just wanna work in your own IDE. Right. Then yeah. Why should we you know? Why should we have to go and context switch between all these different tools when you can just work within the scope of your own IDE and query that entire SCLC for just the data that you need on a day to day basis. Right? Yeah. That's the Nirvana state. Right. The future. Right? You're choosing future. The, the AI piece of it all, but I will get there we'll get there soon tonight. So before we show and and stop telling people, right, why don't you tell us a little bit about Cloudways Unified? Fantastic. Look, this is this is great. Right? In very simple terms, what does Cloudways Unified provide? So it it literally provides the capabilities across these four foundational stages that we know of today. Right? There's build, there's test, deploy, and secure. So there are other stages, no doubt, in an SDLC. There's the pre, you know, the the the pre build stage, and then there's the post operational stage. Right? So but the fundamental building blocks are these four. And then the heart of it, with you probably Unify, you can use, you know, Jenkins open source. Unify itself is built on Tekton, Kubernetes, so it's bringing you into the new age. Right? Mhmm. You can use GitHub pipelines and GitHub workflows. GitHub actions, probably, Unified itself comes with actions as well that you can extend your pipelines with. The other aspect of this is using any SCM provider. So imagine team a uses GitHub. Team b uses GitLab, SCM. Team c uses, Azure DevOps. The ability to bring all these different, repositories, right, into one place and provide that layer of visibility. Any ticketing system. If you think about how our TLCs work today, change management in the software world is typically done at the build test area. This is where the developers work. They work with tools like Jira. However, when you look at it on the opposite side of that spectrum of SDLC where you're deploying to production tools like ServiceNow come into play. Yeah. Right? So you need to tie that as a feedback loop entirely from end to end. The problem happens in production. You know, a ticket gets submitted or or generated in ServiceNow, which triggers a ticket in Jira, which triggers a change. Developer is notified. They go build. They go test. They deploy. Make sure that everything is secure before it gets deployed, you know, into their environments. So that whole set of actions can occur within one control plane. You make it sound pretty nice. They're on a street. Right? True near Bonnet Street. So probably Unify collects the data from all of them and lets you and your team, and or AI agents, we'll talk about AI agents in a second, orchestrate them all from one place. So Right. What we've done now with the enablement of AI is we've added, the Cloudways Unified MCT server. Right? This enables developers, platform teams, agents of any kind to interact with the delivery process via natural language within their ID or using a, an agent front end. You know, I'll I'll demonstrate that with with Bruce here shortly, but it literally allows the surf surface, I should say, surface area, and give you those actionable insights instantly, right Mhmm. By just providing natural language input and getting that information really, really fast, as you develop. Yeah. And we should mention the solution's great, right, on paper, but it speaks for itself in our customers. Our customers have cut development, build, and deploy times by 75%. They're onboarding products faster. They're detecting and remediating failures in minutes instead of hours. And they're doing a lot more. Right? We're seeing a lot of results with with this unified control plane and our and the power of our CI solution. Absolutely. Every customer that we've onboarded has improved their delivery time significantly. Right? They all vary because of their sizes and the amount of applications that they're deploying. But in every single case, they've cut their development time. You know, they've cut their deployment times by x amount. You know, they're building projects a lot faster because the onboarding of develop developers a whole lot faster as well. So Yeah. Yeah. Absolutely. Well, we shouldn't hold it off anymore. Right? You wanna jump into the demo for us? Yeah. Let's do a quick, demo. Let's see. I think I need to share my screen. So if you think about Cloudways Unify, we provide a suite of dashboards that give you data across your entire SCLC. There's the software delivery activity dashboard, which shows you the number of components you're building, how many workflows are running against those components, what those workflow runs look like. Right? How many are successful? How many have failed? Why is this information important? Well, if I'm a manager, a VP, you know, a director, This level of information gives me the data I need to figure out why things are not functioning in the software factory. Right? Right. Right. I can I can look at security insights? For example, this, by the way, works with our security, packaged security, scanners that we provide out of the box. We call this Unify. And what the simplicity of this is that you just need to connect your repository directly to Clovis UniFi. And by default, it automatically runs these scans. So you can see what those open and reopen vulnerabilities are immediately across your entire component list. Right? In this case, you can see I have 11 high open vulnerabilities. I can scroll down, see which one of those are, are addressing which component, and I can see if they were breached or not. Right? Which scanner is actually running them, etcetera, etcetera. Right. And you can also integrate any enterprise scanners that you have deals with. Like we mentioned, Snyk and SonarQube, you just you can integrate them here too. Absolutely. Snyk, SonarQube, BlackDock, name it. Right? All those common big scanners, that do SAST, DAS, IS, and SDA scans can all be integrated. If you're a small shop and you don't have the investment, you can use exactly what's out of the box and still get, you know, all four types of scans, for your components. Right. Durametrics, out of the box, this is a great dashboard because it provides you what you need to make sure that you're, you know, getting to where you need to from a from a transformation perspective. Perspective. If you're going through a DevOps transformation or DevSecOps transformation, you need metrics like mean time to failure, mean time to recovery, etcetera. Right? So Mhmm. Mhmm. The dashboards give you that great, great insight. Mhmm. What I wanna do was really go through these few dashboards. There's a bunch of other ones, flow metrics, test insights. There's a Jenkins dashboard, Jenkins open source one, that actually also highlights the, different, Jenkins open source or CBCI controllers that you might have, as a company if you're using, Jenkins or or CBCI. Mhmm. I won't jump into that because I think we have a very short amount of time here. Is that correct, Liz? Yeah. Not we gotta we gotta keep it tight. Keep it tight. Alright. So what I want to do here was actually show you what I do from a, from a code perspective. Right? So I want to, use this particular repository and quickly fork it just so that, we can show you what the process is. We're in GitHub right now, and you're forking the repo. Right? That is correct. We are in GitHub, and this is webinar I'm gonna put my name so I know exactly. Sunil webinar two. Actually, I'll give this three. It said two is available, so I'm gonna use that. I'm gonna create a fork. Essentially, I wanna onboard this new repository, onto Clavish Unify. Okay? And then what I'm gonna do is I wanna because it takes a little bit of time to scan behind the scenes, I'm gonna switch over to a, a repository that I had done earlier and, onboard it. So here, I'm gonna create a pull request. Right. Select my, select the branch, create that pull request, and you can see it's pretty easy. I mean, this is something that developers do on a day to day basis. Right. I have to do one more thing here, and understand my workflows. Boom. That's it. Now I know what my, you know, my my repository is. This repository can then be onboarded to Unify very, very quickly. Alright? You can create the go to components, create a component, and pull that particular repository up. Let me see if I can find it. Hackers dash sunil. If I can find it, repository name. Come on. There's so many repositories. Let's do this. I'm gonna go and go ahead, please. Just the repo name without the organization. It might pop up. I've had more success with that. That's what I was trying to do. Packers for Sunil webinar. And there it is. Right? So now I can just create the component. Now what's the beauty of this is that I've not only created the component, but it is now kicked off a scan. Alright? Yeah. What I wanna do is go back real quick to find one of the ones that I had actually started working with. So it's running right now in the background as that connection is made. It's running that implicit security Exactly. With all the Do you remember yes. You remember you remember I said that it starts to kick off those those, security scans? Right. Right. Here's one that I, I created earlier, and it ran, a couple of runs. And you can see here that it's giving me eight very high severities right now. Yeah. The beauty of this is that, particularly for that component, not only can I see that workflow? Right? If I needed to go and edit it, I can edit it, and this is what it would look like. Mhmm. You know, if if I wanted to, I could see the runs, etcetera. But if I wanted to look in the security overview, right, this is this is the information that's at your fingertips. Mhmm. You know, how many open findings do you have by severity? Right? What's the risk accepted, etcetera? If I scroll up and look at the security center, this gives me that information around those CVEs. What's the very high CVE? If I can triage this CVE right here, wouldn't that be amazing? Yes. Right? Now this is the big thing right here. I can look at the details. This gives me exactly what the severity is, what the package is, what you know, all the details around that. Now the beauty of this is that if I wanted to do a triage, I can do that real quick. Right? I can do a fix required. False positive, in this case, I wanna select false positive and say false positive and triage this immediately. Now remember, if if you have hundreds of thousands, if not tens of thousands of these, this makes life a whole lot easier. Right? Because a lot of these CVEs typically are false positives. Right? So now we've gone down to seven. Okay. You see that. Yep. Here's the cool thing. I'm gonna switch over to my agent, AI agent, that, is connected to Cloudy's MCP. Yeah. The Cloudy's Unifin MCP server. I can query these directly from my AI agent that could be in your ID. Now if you're using Versus code, for example, you know, let me see if I can actually bring this up here properly so you can actually see it. Well, the the behavior is the same. Right? You have the the window open for the AI agent, but you can also do the same behavior in your ID no matter what your ID is. Yes. And that's exactly what I'm trying to prove. Right here, I've said list out my components with the hackers organized sub org that have the term four web. You probably can't see it here, but I'm gonna hit send so you can see that. Yep. So you see it right there That have the term four West four r g, that's the same component. So there's my component. Now if I say list the number of CVEs for the West WES test four r g component in the hackers organized sub org. It should go out and grab the same number of CVEs that you see here. Now the beauty of this is that this information is directly the same as that that is in the UI. Okay? So you can see the beauty of working in this. Right? Seven CDs. There you go. Right? So you can see I'm gonna switch over here. Right here, you see seven, and right here, you see the same number of it the same amount of information, in the UI. So what I was trying to prove here I'm gonna stop right there, Liz. What I was trying to prove here is that the information that's in the UI is the same in your AI agent which can run-in your IDE. Mhmm. Pretty great. Okay. So which is amazing. Right? The developer productivity just shut up because they don't have to contact switch. Yeah. They can be in their ID. They can just work what they work with on a day to day basis. You're meeting the developer where they are instead of making them go to Exactly. Yeah. Exactly. Exactly. Alright. Thanks for that demo, Sunil. And we should mention I I mean, the next webinar, I don't wanna tease too much. We're gonna focus more on that security piece of it all. But you we spent a lot of time in the components, but it also is available at the application level. So that can be important for a lot of organizations who wanna see across an application what their security Mhmm. Makeup is like. Right? Yeah. Yeah. Yeah. I think I think that's gonna be a a cool one because if you think about it, in most cases, developers do their stuff and then they have to package or send their information over to a sec team, right, that analyzes their code base. Here, now, what we've done is not only bring we've shifted left. This is the true essence of shifting left. Right? Yep. It's not about putting the burden on the developer, but we're actually enabling the developer to work faster, more efficiently because the data is now in their control. Yep. Right? Yeah. So we're able to analyze. Yeah. Yep. Yeah. Pretty cool. So bringing it back to Alex here since we followed her on this journey of her her pain in the the SCLC and her little teams. She chose to use CloudViz Unify to consolidate all her siloed systems under one roof, under that control plane. And what she's able to gain is access across these pipelines and systems and teams, and she's able to automate security checks, establish best practices, and streamline critical items like auditability and her scalability that she's been reaching for. And her developers didn't have to re platform. They didn't lose a month of productivity. They didn't have to rip and replace. They were able to just keep doing what they were doing. But now Alex can see everything under one roof, and she can show it to her managers. She can report upwards and downwards however she needs to, and she can help with those Monday morning issues that she tends to run into and and, hopefully, streamline them so she doesn't have as many in the future. Go copies Unify. Yeah. And here's a quick note from one of our customers who's on Cloud Views Unify. It highlights the our our need for not needing to or our, benefit of not needing to rip and replace or replatform their entire SDLC. It's from Synaptics. They needed to get visibility and velocity, and Unify was the solution for them so that they didn't lose one of the productivity. Yeah. And and every customer that I talked to that has started to use Unify is a very similar, statement, right, that they have that they have. It has definitely helped them. In some cases, they helped them in certain areas more so than others. Mhmm. But overall, the sentiment is that this is helping us do things a whole lot faster, more reliably, and with a lot more visibility across their entire CLC. Yeah. Yeah. The benefits are awesome. So what should you remember from this webinar? CloudMuse helps you deliver faster, achieve velocity at scale, and eliminate waste with no rip and replace or replatforming. And we can integrate with any CI. Any scanner that you have, we are trying to meet you where you are and optimize what you already have in place. Fantastic. Love it. I love it. Absolutely love it. And cup customer impact. Right? We we covered this in the our last webinar. We've been empowering developers around the world for more than fifteen years, and this is just the next step in our evolution. And we're really excited to see what Unify can do for organizations that are looking to scale and grow without all of those replatforming issues. Yes. We are redefining the future of DevOps. Right? We are trusted by Global two thousand and backed by its thriving developer community. Yeah. Absolutely. And that's it. You've seen Cloud b's unified. You heard about the challenges in one of our real world scenarios, but we hope you've enjoyed today's webinar. We teased it earlier. The next topic we're gonna cover is continuous security across your pipelines. So if you're looking to make security contextual and built to scale without slowing down innovation, we hope that you'll join us for the next one. Thanks, Danielle. Fantastic. Thank you, everybody. Thank you, Liz. And, talk to you guys again soon. Okay. Have a good one.