Name: CI/CD at Scale: The Blueprint for Enterprise Resilience & Efficiency
Uploaded: 2025-09-18T18:01:10.619Z
Duration: 45 min 8 s
Description: CI/CD at Scale: The Blueprint for Enterprise Resilience & Efficiency

Transcript for "CI/CD at Scale: The Blueprint for Enterprise Resilience & Efficiency": Hi, everyone. Welcome to the webinar. I'm Liz Ryan, your senior product marketing manager here at CloudVees. And today, I'm joined by our global field CTO, Sunil Movadia, and we're here to talk about CICD at scale, the blueprint the blueprint for enterprise resilience and efficiency. Thanks for joining, Sunil. Hey. Thank you. Thank you. It's a little early in the morning. Right? So we all have our full pause. Haven't had my cup of coffee yet. So Oh, no. Glad to be here. Alright. We'll Yeah. Kick this off. Starting with the agenda, we'll talk about the the challenge of DevOps at scale, how to modernize your CI for peak efficiency, and simplifying tools for all with one single solution. So let's start with the challenge. Right? So the stakes of software delivery are higher than ever. As we all know, product launches are faster. Security threats are larger. Tiny bugs can lead to massive outages. Downtime costs are climbing, and we've all got those compliance headaches, that manual work that's taking time away from our productivity. Everyone's trying to scale and scale fast, but we've all got these complex webs of systems and tools and teams across the globe. We're using on prem. We're using cloud. We're using everything in between. Right, Sunil? That's the truth. Right? So the fact is that, if you look across the the entire SDLC for any single company, especially the large ones, you'll find that not only is there tools sprawl across every single aspect of their SDLC, but the fact that they're all fairly disconnected and you cannot see, you know, in a single pane of glass view what's happening across the entire, you know, software factory, so to speak. Right. It's a pain for everyone. Everyone's got a 100 tabs open at a time, hopping into different tools. There's there's no way to consolidate it all. And there's a lot of context switching. Right? And this is where I think developers lose lose a lot of their efficiency. So Absolutely. Yeah. And so when we look at how Jenkins the fact is that Jenkins is a very, very, very well known automation utility. Right? And in most cases, companies that are starting out will definitely look at Jenkins and end up with a controller that grows over time, and that's that monolith that, you know, we encounter all the time when we're talking to our prospects and our customers. Or on the other hand, they might just install controllers all over the place. Right? And so now you end up with this island of Jenkins with disconnected servers for different teams or geographies. Even though teams do enjoy a great amount, of autonomy, this re erases the admin costs. Right? Why? Because there's a lot of administration that needs to occur across all these servers. On the other hand, if you are a monolith, right, it is centralized, but it is not scalable. So if you have teams that range in the hundreds of thousands of developers using a single server that tends to not only limit scalability, but that impact when the server goes out is massive to the entire company. Mono I mean, the word monolith alone just sounds scary. It just sounds like pushing a boulder. Yeah. Pushing a boulder up a hill. Right? That's just Exactly. That's what it feels like to operate that kind of system. It does. It it does. And that's usually how how, any Jenkins administrator will tell you that's exactly what it feels like. Right. And they're probably all asking how did I get here? Because when you start out with Jenkins, it feels easy. Right? And it is easy to start. But then it just explodes and becomes Absolutely. Overseeing the dream. That's the beauty of Jenkins. Right? So it's easy to set up. It's easy to get going. But the thing is that most people don't have the foresight of where they might go with Jenkins. Right? And that scalability that they're and reliability that they're not thinking about comes to haunt them years later. Absolutely. And, I mean, we're talking about Jenkins, but this is a DevOps tool problem. Right? This happens with every tool. Developers find the tools they love, and then it just explodes. Yeah. And it becomes a velocity problem because there's tools all over the place. Nobody's talking to each other. It becomes slower and slower, more complicated. Right? So absolutely bless developers for bringing in new technology, bringing in that new blood that we always look to improve how we deliver code to production. Right? Right. But with that comes the complexity of having to manage these different types of tools all the time. Right? Jenkins is just one of them. And so when a developer brings in a new tool set, it becomes a challenge of scalability, of reliability, connectivity, visibility. Like, there's so many hitties. Right? That Exactly. But it just becomes it's not just the Jenkins problem. Like you said, it is a velocity problem that impacts the company, you know, as a whole, which leads to dollars. Like, that's that's just loss, right, that we talk about. Absolutely. So, you know, this is where Clovis comes in. Our vision has always been to continuously redefine what's possible through software, and our mission is to really empower developers to build better, faster, safer, and more reliably. Right? And so at the end of the day, you know, the mission being go faster, build safer skill you know, better scalability, we want to give customers the best of both worlds. Yeah. You know, provide a a one to many view of Jenkins controllers, the ability to manage the plug ins within all those controllers, right, and provide governance across their entire infrastructure. Now this creates a better experience for the administrators. But at the end of the day, the ROI for the company, the value for the company is that reduction in time spent on managing all those controllers across the entire company. Right? And so now that automation at scale comes into play, we can provide better, built capacity through workspace caching, for example, right, the but For sure. And and the high availability, high high scalability, you know, features within HobiCI, help you manage that scalability and reliability across your CI infrastructure. Mhmm. And you're already getting into the, the features here. Yeah. But I just talked yeah. And I just talked a little bit about those features, right, for for from a Jenkins open source perspective. So for those of you that don't know, what CloudBees or who CloudBees is, we provide 75, 80, you know, contribution to the Jenkins open source community. Right? We're at the top of that list. You go to Jenkins and you can look, and we are right there. Yeah. We're at the top. Right? Very active. And so, exactly. And so the those that 30% extra that we provide are those high, you know, enterprise grade features like, high availabilities, you know, horizontal scaling, workspace caching, pipeline templates, and task, etcetera, that leads to the better support for your Jenkins installation, your Jenkins infrastructure. Right? Now you add to that a tested and supported distribution, that's very secure. Of course, our distributions are all, you know, secured, so that companies can be, you know, can can not worry anymore. Yeah. Like, the the plugins in Jenkins alone are hard to manage when you're just using the open source version. Exactly. Exactly. That manageability, it's just from a plugins perspective, is a nightmare as it Right. You know, as as we as you and I know. And so for us to provide the supported tested version, right, with programs that come behind the scenes from professional services, TSM, ISP, you know, and training, perspective, this is where, you know, people get the peace of mind. Companies get the peace of mind with their Jenkins infrastructure. For sure. And you're tapping on the infrastructure, so I'll I'll move on here. There you go. So so, you know, this is this is that whole, monolith versus, you know, gen Jenkinsstein, as we call it. Right? So every team ends up having their own controller, and then they end up doing their own pipeline development with shared, you know, agent pooling or trying to set things up. The problem here is that when you end up with this scenario with open source check ins, now the manageability factor just skyrockets. Right? And so as you add different teams and additional developers with pipelines that span into the hundreds, if not thousands or tens of thousands, that scalability feature just tanks. Right? And so this is where with Jenkins or CloudBCI, and its enterprise grade features, you can now create a layer of management with the operation center that lets you not only manage the controllers, but lets you manage all of the plug ins within those controllers that you, you know, do RBAC, shared agent pooling, you know, and a whole slew of features that we that we can talk about here, in a short amount of time. Right. It takes away the pain of flipping through tabs, trying to contact different teams in different time zones. You can actually look at everything in one place and not lose sight of an old plug in, an upgrade you missed. You can just use Hubby's and they'll do for you. And if you and if you think about where, you know, most administrators for Jenkins CI sit there, you know, in that shared services platform engineering, you know, IT infrastructure teams, a lot of times, they either don't have that deep Jenkins CloudBCI knowledge. Right? Number one. So they need an easier way to help manage that infrastructure. Or two, they are based in a team where they have other responsibilities other than just managing a CI controller. Right? And so with the ability of having to manage this through one single pane of glass view, is a huge benefit. Yes. Absolutely. So we're gonna jump into the features here. We've talked about CI at a high level, but I think it's important for us to talk about the actual infrastructure and some of the really differentiating features that we have that can help cure this pain of sprawl and inconsistency in the Jenkins Stein of it all, which I love that our little Yes. Jenkins Stein icon. It's a very famous, sticker. Actually, people ask for that. I want it I want it for my laptop. I want, like, the Jenkins time on my laptop. Definitely. They're very, very popular. That's for sure. So let's talk a little bit about Cloudy CI architecture and components. I think one of the biggest things that we've released from a feature set is, you know, high availability and horizontal scaling. Why is that important? Right? If you think about the transition of going from VMs to Kubernetes, right, the admin or the, you know, the introduction of Kubernetes gave that scalability factor, and it added these sets of features that, you know, tended to give a lot more reliability to whatever you put into a Kubernetes cluster. And so we've taken advantage of that. Right? And so with high you know, high availability, horizontal scaling, we can now let, you know, companies scale on demand. So if a controller goes down, another one gets spun up, all the jobs that were running on that controller that was going down can be moved over to the new controller. Right? Pipelines or you know, that that might get affected during, a during a run, can be transitioned to a controller that has more capacity. Mhmm. And that can all happen behind the scenes. Like an embedded insurance policy almost. Hey. You know, that's actually a great way to put it. Yeah. Yeah. That's a great way to put it. Right? And if you think about that insurance policy that you need without putting hundreds of developers out of commission for the short amount of time that your controller goes down, that insurance policy pays for itself right off the bat. Exactly. Yeah. Exactly. So so with things like, you know, Linux agents, shared build agents, etcetera, those great, features are now just built into CloudBCI. Right? And as you look through, all these different usages, you know, as your teams grow and expand, you wanna minimize the complexity of managing your teams and controllers with the CloudBC's operation center. Right? Provide that unified user experience, in instant control of provisioning, for example, shared agent provisioning. Configuration as code or task for management is another key feature that a lot of our customers use today out of the box. It is probably one of our most common features, you know, above and beyond, like pipeline templates, you know, pipelines, catalog, for example, the operations that are cast by far is one of those things that, you know, a lot of our customers use. Plugins give, you know, CI is flexible architecture, but they can also take drain the time, of an administrator because if they have to go and manage plugins controller to controller, that becomes really painful. Right? Yeah. Yeah. We've done what we've done is provide the Klaviyo's assurance program app, which lets you not only upgrade your plug ins, but since we test over 250 plug ins and help manage and maintain them, we give you the most common plug ins out of the box. Right? So that's our tier one plug in. Our tier twos are those that people can still install within their, probably CI controller, you know, which we test against. So there's some level of assurance. Then there's the third tier, which, you know, if you develop your own plug in or you bring in something that is not managed, those those fall in the third tier. But the fact that you have this access to supported plug ins is, another, you know, I should say, peace of mind. Right? Apps well, especially for you mentioned the if someone's on a team and then this isn't their full time job, for instance, how are they supposed to monitor every security vulnerability or patch that comes through on every single plug in they've installed in their Jenkins and make sure that it's up to I mean, the headache alone with monitoring that ongoing is a lot for one person that already has other responsibilities. Right? Absolutely. And, you know, you don't get me on the pedestal here about security because there's really something that you and I will be talking here pretty soon about security. Right? But Right. That is another thing entirely that causes issues not only at the infrastructure layer, but at the app layer as well. Right? For sure. So yeah. But, you know, finally, like, from a pipeline management perspective, you know, the pipeline template catalog provides a collection of pipelines based on best practices. This is perfect for platform teams, shared services teams, where they need to create catalog that developers can just reuse. Right? Mhmm. Yeah. Keep keep that practices in house. Right? Exactly. Like, you you mentioned security. Right? If a security check needs to be added to a specific, template, they could add that, and then that is just reused by developers so they don't have to go program script it out. Right? It's just part of our it's part of a template. That's great. Security. But yeah. I know. So here we go. Right? We talk about security. So now when when we release our distributions, you know, we provide an enterprise ready, tested, validated, secured version of Jenkins. Why is this important? Right? These these hardened versions of our, you know, containers, container images, are crucial to enterprises today because they the last thing they need is a vulnerability in the software they're using to create the software that they're developing and deploying. Right? And so they this is just a peace of mind for them. You know, additionally, you can standardize team environments by creating bundled configurations with CAST, for example. Right? Mhmm. RBAC, flexible role based, you know, access control model, single sign on, enforcement of controllers and agents, you know, through using folder hierarchies. These are just small pieces of a very large suite of features that we have in CloudBCI that really help, you know, teams that have massive distributions of Jenkins controllers or massive, you know, developer team sizes. Right? And so when you look at that scale in general and you look at how the number of pipelines that get created by development teams as they grow, as the number of applications grow, the number of pipelines grow, the number of Jenkins controllers grows. Right? It just becomes an exponential headache if you don't put a layer of operate operability, security, right, reliability, all those great things that that we provide out of the box. Yes. All the illities that you mentioned earlier. Right. Well, I know we've been talking about high availability and horizontal scalability. Right? So, as I call it, you know, enables, load balancing and protection against a single point of failure. It can spread its workload across multiple replicas and keep them in sync. The it does this automatically. You know, so now your outage is reduced to near zero, for example, better or increased efficiency and productivity of your dev teams because you don't have to worry about, you know, failed controllers. And so this level of reliability ensures that the developers keep working and doing what they do best, right, which is developing code. We don't we don't need them to go troubleshoot a controller. We don't need them to go troubleshoot pipelines. Right? So but Actually, they don't want to either. Exactly. If you if you talk to a developer, I you and I have both talking to developers many times. Yeah. And what is the first thing that they say? Look. I don't want to go and troubleshoot pipelines. Right. I don't want to go and switch between different, you know, systems and utility. Look at logs in different systems because I spend 70% of my time doing just that. Right? Yeah. It says coding, which is what they've done in here. Instead of coding. Yeah. So by saving developers days typically lost to optogens and system failures, you know, frees them up for time for innovation. Right? So development teams can invest more effort into creative, problem solving and developing new features, driving technology advancement, and and and creating that competitive edge for their company. Absolutely. So we talked a lot about all these features that CloudBCI has. Right? And that's just part of the CI process, but software development is so much more than just CI. And Right. What if there was a way to integrate all of that activity, not just the CI, but the build, the test, the deploy, everything under one roof under a single control plane. And it would eliminate context switching, those hundreds of tabs, you know, universally enforced best practices, security standards, help with delivery. What if that was a possibility? And what we're here today to talk about is CloudViews Unified. Right? We're we're giving people that possibility because Yes. Yeah. And we we know that it's not just about the tools and the complicated SDLC. It's also about the fact that all of these companies around the world have a mix of tools, whether they're on prem or they're in the cloud. They're on a journey. They're not just shutting down operations for a year and ripping and replacing. Right? That's not possible for the way that they need to deliver based on demand. So what are you seeing, Sunil, in the market today with the the what types of companies are having these problems? Do you think it's a majority of companies that are having this problem? I think the term that you used was rip and replace. If you think about it today, companies today have invested a significant amount of money in the tools that they bought and purchased. Right? Absolutely. They are not going to spend the time or, you know, a two, three, five year cycle to go and rip out something that they've invested millions of dollars in. Right? And so one aspect of this is that they need the ability to continue using those tools and, over time, phase them out as necessary, right, or as they see fit. And a lot of companies out there today have this rip and replace methodology. It's either my car or no car at all. Yeah. Right? And if you think about that, that's not a viable option. And so what I see today, a lot of companies and you'll find this in a lot of the large fintech, you know, enterprise grade companies that a lot of their infrastructure is in the traditional, right, VM infrastructure. Mhmm. But they all have this journey going into the cloud. They all want to be pure cloud native at some point, but they are still stuck. If you think about the concept of the mainframe, what was it? Mhmm. Twenty years ago, people said mainframe was gonna go away. And you and I know very well today that there are so many banks that still have been there. They can't let go. There's no way. Right? And so you still have to maintain the traditional infrastructure. You still have to, take care of those applications that bring in the money. Right? Mhmm. And then you have to accommodate those, applications and teams that are moving to the cloud slowly but surely. Right? And then you also have to accommodate those teams that are already in the cloud. How do you bring all of that together? Well, in a lot of those highly regulated industries, like you mentioned, fintech, government government, for instance, they have compliance standards that they have to meet that a lot of those on prem solutions that that's the only way half the time someone if they need to be FedRAMP certified, it's probably not gonna be in the cloud today. Right? I mean, that's that's a hard part. Difficult. Very difficult. And you bring up the word compliance. I mean, if you think about, you know, we could we could regulate a lot of the delivery of software in the SDLC. Right? How do you add this layer of compliance on top of that? That's another topic for us to discuss another day. Yeah. This layer of compliance that, you know, we need to put some set of rules to address maybe a country's compliance requirements, right, or some specific set of requirements around maybe SOC two or SOCs. How does that, you know, apply to the software development life cycle? Right? That's a really good conversation to have at some point. Yeah. But, well, you're talking about the layer of automation and the the layer here, like, what we'd like to call the control plane. So let's let's talk about Unify. Absolutely. Right? So now think about CloudBCI for a second. Cloudy CI is one of the greatest, you know, automation utilities out there. As a matter of fact, if I recall correctly, maybe you and I did some research around this, but there's over 50, maybe 70,000,000 users of Cloudy's or or sorry, of Jenkins alone. Mhmm. Right? If you think about that installed base of people out there who are using not only Jenkins open source or Cloudy CI or CircleCI, right, that layer of CI users across the globe is massive. And the fact that they're all mixed or could be mixed in a single company is another aspect of Yeah. Complexity that people don't usually think about. Right? And so that automation and visibility across your entire SDLC should include not only tools like Jenkins open source or CloudBCI, but any other tool that you're using. Right? And so during your build, test, deploy, secure stages, right, or, you know, postproduction as well, you need to be able to, one, use the tools that you already have, connect them to a control plane that gives you that visibility across your entire SCLC. Right? That includes, ticketing systems, for example, like Jira on one end and maybe ServiceNow on the operation side. That could be your production deployment operations post production. Right? So and then connecting those through one layer, you know, and that gives you the full visibility, that full audit control, right, that that you need. Now on top of it all, if you add that AI powered automation and visibility layer, now your developer can sit within the scope of their ITE and get all that information through natural language input, right, and get that visibility across that entire SDLC. Instead of leaving their ID. Yeah. Exactly. Either. Exactly. Every actionable insight is now available immediately at your fingertips through just natural language. Yeah. Well and you mentioned a wide variety of tools. For instance, if a team has pipelines in Cognigy CI or Jenkins or GitHub actions actions or other CI tools, other source code management tools, you can integrate them here, which is really powerful. You're not making teams transition to one single CI. You can just integrate all of them. That's that's a really good point you bring up, Liz. So, you know, GitHub actions is very popular. We know that. Yeah. Right? GitHub actions, GitHub workflows. The biggest issue that most people has is that if they go to a CI tool other than, you know, GitHub workflows, for example, you have to relearn that tool. Yep. Right? Yep. Whereas with Unify, you can not only ingest, you know, your GitHub workflow, but GitHub actions become part and parcel of your day to day activities. You can also use Cloudy's actions if you wanted to. You, you know, create the workflows in Techton, and combine the two to do different things at different stages, in your SDLC. That level of flexibility is where Cloud's Unify comes in. Absolutely. Yeah. I wanna be mindful of time, so I'm gonna keep keep us moving. Yeah. Sure. As you already heard, no rip and replace with Unify. You can use the tools that you have, and it creates a frictionless developer experience, and they can keep moving, and you can get better visibility and better best practices and better security. It's just all better with Unify. No doubt. No doubt. Right? And so when we start looking at how developers use it, they want some cell sort of self-service capability, but in use the tools and technologies that already have, the YAML DSL. Right? But have Right. Extensible, flexible workflows as well. Right? Feed your own tools. Don't care. From a platform team perspective, having an enterprise organizational model that lets these platform and shared services team manage the entire organization. Perfect. Right? That governance, consistency, and security all within a centralized, you know, control plane giving you visibility across the entire SDLC through these through these dashboards. You know very well DORA is like a very well known metrics collection set of standards. Mhmm. Out of the box, you Unify gives you information not only on DORA but also the Jenkins CI controllers that you have today through Jenkins Insights. Right? So how how awesome is that that, you know, Unify not only provides the security insights across the entire organization, but as a Cloudy CI or as Jenkins, you know, administrator, I can use the Jenkins insights capacity within Unify to provide even deeper insight to what's happening within my Jenkins infrastructure. It's great for reporting. Definitely. When you when you gotta report those results to the higher ups, it's great for reporting. Without a doubt. Without a doubt. So let's talk about our customers. Cloud Visa has been around for fifteen years. We're not new to this this gig. We we have a lot of major customers. We're trusted by the global 2,000, and they've seen a lot of success with us. So, Sunil, do you have any examples of some customers or a customer that that's had some success with Kavi. Look. I I think all these are amazing, you know, customers that we've already had. Now if you look at just a couple of these, I'll pick on Salesforce and IRS. Right? So the extreme here is that IRS is a government entity. Right. Not so fun. Not so fun. Not so fun. You know? I know. It it brings it brings back, some angst to a lot of people. I get it. But the fact is that IRS requires a secured version of CloudBCI, right, or our unified. And so these are the Highly regulated. The highly regulated, environments. Right? On the other hand, Salesforce is that forward facing, like, everything in the cloud kind of environment. And so, you know, from a software factory perspective, we provide that scalability and reliability using, you know, products like Bravyi CI and CDRO and, you know, compliance in that lower layer with Unifi providing that feasibility that a developer or a team lead or a Mhmm. Director, VP level needs across their entire SDLC. Right? And so this message that how probably CI and UNIFY play together resonates across all of these companies today. Yeah. From from the bleeding edge of technology all the way to our our friends at the IRS. Exactly. So we already mentioned. Right? We're trusted. We're backed by a really great community of developers, and we're also trying to change the face of DevOps with this anti platform leading mission. Right? And that we're trying to stay away from making people rip and replace and having people choose their own adventure, but choose it with a level of measure and strategy and scale, making sure that they're set up for the future. I love that, Nicole. And no. No. You're fine. You're fine. It's it's I just wanted to press the anti platform thing. Right? Why? Because Yeah. Yeah. One one, the whole idea of a platform and having being enclosed in a ecosystem that is only relevant for those people using it at that time and you can't bring in anything else is not the way, you know, developers work today. Right? They want to be able to use the technologies that they want to use today. And so that anti platform message, I think, is is very crucial and the fact that, you know, we are not a rip and replace company. Right. Right. Right. And it's not gonna take hours and weeks and months to get it all together. You can integrate with us within a matter of minutes through. We yeah. Exactly. We see the benefit literally within minutes. The minute you ingest your repositories, your security stuff starts to, you know, give you data back. Your workflows can be ingested immediately and start running. So the the the go to market, you know, is almost the benefits are almost immediate. Yes. Yeah. And circling back to our challenge of the day, DevOps philosophy, to achieve it, you really need scalability, reliability, and visibility through that single control plane. Yes. Agreed completely. Right? And that single control plane where you where it provides the visibility, which becomes one of the like, a it's like watching a a a show that you can't get your eyes off of. Right? Yeah. Yeah. You need that visibility into your SDLC. So this is where I think the whole idea of Unify comes in with CloudBCI providing that level of stability and reliability and scalability that is so needed. Yeah. Absolutely. Well, being mindful of time, I will wrap this up here. This is one in five in our series of webinars getting people up to speed on what CloudMuse has been doing and and learning more about DevOps and how to optimize it. And, we'll be sending out more info very soon within the coming weeks for for our next webinar with me and Sunil. So find us find us back here. Fantastic chatting with you, Liz. Yeah. Thanks, Sunil. Thank you so much. Thank you, everyone. Thanks, everyone.