Jenkins Project Continues to Gain Momentum – Fatih Degirmenci, Linux Foundation and Sacha Labourey, CloudBees
Alan is joined by Fatih Degirmenci, executive director, CD Foundation at the Linux Foundation, and Sacha Labourey, board member and chief strategy officer at CloudBees, to discuss the momentum in the Jenkins project across several vectors. They dive into the continuing dominance of Jenkins as the CI/CD platform of choice, as evidenced by growth in Jenkins Pipeline jobs and total jobs/workloads run on Jenkins, as well as support from industry heavyweights and the active, vibrant Jenkins community/committers.
Transcript
This is Text Drunk tv. Hey everyone, welcome back here to Tech Drunk tv. You know, for those of you who watch Tech Drunk tv, you may know that we once a month do a nice video series where we take a deep dive.
And the name of the show that we do that is called CD Pipelines. And it's a, a, a co-production of us here at Techstrong, along with our friends at the CD Foundation, part of the Linux Foundation. Now, this is not a CD pipeline, but it's a special CD foundation sort of interview, and I'm happy to be joined by actually two board members from CD Foundation.
Uh, one you may recognize from our CD pipeline show. It's, uh, Fadi Digger Manchi, and if I mispronounce it, Fadi, it's hard for me. I try.
Perfect. Um, but welcome Fadi. It's good to have you on.
com. I've been working with him for 10 years. It's my good friend Sasha Lare.
Uh, Sasha is the, I said, a board member at C D F, but he's also co-founder and chief strategy officer at our good friends at CloudBees. Sasha Fadi, a pleasure to have you both on. Welcome to Text Drunk tv.
Thank you for having us, Adam. It's a pleasure. Um, so, but today we're gonna talk Jenkins a little bit, right?
For those who maybe, I think everyone in our audience knows Jenkins, but I don't know if everyone is aware that actually Jenkins was, uh, weeded over or given over to the management of the CD foundation. Had to be about four or five years ago, Sasha, wasn't it? When the CD Foundation took over Jenkins?
Yeah, yeah. Appro, yeah. Approximately four years ago when, when the C D F was created, essentially.
Yeah. I think it was 2019. Yep.
And so it's, it, and it's one of Fadi, what is it, one of eight or nine projects within one Of nine projects. Jenkins is one of our co uh, founding projects and one of nine at the moment. Yeah.
Yep. And again, our audience is familiar, but Jenkins is the backbone for many C I C D, uh, installations at many, many hundreds of thousands, if not millions of organizations. com in 2013, DevOps was Jenkins.
Someone once said, uh, DevOps is the symptom. CD is the cure, and Jenkins is the medicine. Right?
And, and you know, Jenkins probably had 90% plus of the market. There were thousands of plugins. There's still thousands of plugins for it.
But of course, over the 10 years we've seen, we've seen other projects. We've seen other solutions come to market. And people, you know, we live in a, an industry unfortunately, of shiny new toys.
Everybody likes to see the shiny new trinket, and they're attracted, and they almost take for granted what, what works for them every day. And we lose sight of just how embedded, if that's a good word to use Jenkins is. But recently, CD Foundation did a little bit of a research, a little analysis, a little study, and they came up with some great facts.
We're gonna share it today on the state of Jenkins. Fair. Amazing.
Let's do it. So I guys, I, I shot my load. That's it.
I, I've given you all the setup. I'm looking for you two to take it from here. Sasha Fadi, tell us about the state of Jenkins, Maybe just to, uh, that's some of my personal views around Jenkins before we perhaps talk about the latest.
So, I'm, I'm an engineer, like, even though I took this role at Linux Foundation, leading foundation, I spent years, you know, building pipelines, running C I C D systems, working with, you know, large organizations as there as open source committees. And as you highlighted, Alan Jenkins is like there. Jenkins is kind of part of like what Aaron is doing.
Like some organizations may be looking at other technologies, but I'm sure many of those organizations have lots of Jenkins installed, either by central IT or by, and I consider Jenkins as critical piece of like production systems, which I call like, it's more than pipelines, actually, production systems that actually let organizations to get those products from idea to code, to, you know, testing, to release, and finally to, you know, production environments. And Jenkins is, I think it's fair to say it's kind of backbone for these production systems. Obviously, innovation is happening within open source.
It's impossible for innovation to slow down. But again, Jenkins is part of critical infrastructure, if you put it that way. It's not just part of critical C I C D infrastructure, but part of critical infrastructure because people are using Jenkins in different ways.
Like some people might be just constantly using Jenkins for content integration purposes, but others might be doing some things we may never think of. So that's why it's like important to understand how critical Jenkins is for the world's know production capability. If you put that that way.
And the numbers you mentioned, I think such a might help us with that part. That also highlights that Jenkins is the, is it'll continue to be an important piece in this complicated, you know, way of developing software lately with all new paradigms and, you know, increasing complexity and so on. Absolutely.
Sachi, you have views on that. Don't wait for me to call on you. Go ahead.
No, I, I love how Fatty talks about critical infrastructure, because that's really what it is, right? Um, it's, uh, 18 years old now. Uh, imagine 18.
How many projects after 18 years old have hundreds of contributors every day contributing value? And it's not, uh, you know, hobbyists, quote unquote, are very important. I started as a hobbyist, and that's amazing.
But we're talking about big companies like a s like Atlassian, like, uh, you know, so many organizations contributing value to, to the project. So in 18 years, Jenkins has been able to weave itself into so many places, into so many pieces of infrastructure. It is indeed critical infrastructure, and it's to be treated as, as such, um, and when you see the growth that it's still going through, uh, it's, it's not static, right?
It's not just something that's left here, uh, and, and, and sleepy. It's something that's very active, very lively, lots of, uh, new things coming up, but also a lot of work being spent on, on making sure that Jenkins remains strong, uh, remains scalable, uh, because it's critical infrastructure, right? It's easier to have cool and fun stuff left and right, uh, with, with new project, because the responsibilities are relatively low.
Once you start having, uh, uh, big families and grandchildren and, and, and whatever, uh, can happen in in 18 years, um, you know, that, uh, the burden is not the same. And, and I think the, the community is, is, uh, embracing that responsibility extremely well. Absolutely.
So, gentlemen, if you don't mind, I'd like to dive in a little bit into some of the findings of, of the state of Jenkins. Um, I don't know which one of you would like to take the lead, but feel free either of you. But, you know, I always like to say, can you give me three key data points that give people a good flavor?
Right? And, and the other thing is, I'll tell you, so you're both in Europe, but here in the US every year the, the president does what they call the state of the union address to a joint session of Congress and the whole government. And, and invariably the president stands up and says, I'm here to give you the state of the Union.
The state of the union is strong, right? They never say the state of the union's bad, or the state of the union's weak, or it's always the state of the union is strong. So I'm gonna assume that the state of Jenkins is strong.
Why is it strong? Show me where, where, how do we know it's strong? Sasha, go ahead.
Well, I'd, I'd love, uh, fatty, you wanna, you wanna start? Yeah, go ahead. Yeah, I think it's like, it's great to talk about, you know, how things are going, how great things are going, and so, but it's also important to support these claims with actual numbers, actual data from the field.
If we think about the production and ments as our fields as CD foundation, the increase in news and adoption of Jenkins continues to be strong. For example, the, uh, increase in number of like usage of Jenkins pipeline jobs over the last two years is around 79%. But that actually shows that people are actually creating new pipelines over and over, and it's like adding new functionalities, introducing new stages within their pipelines and so on.
And this growth, ten nine percent between 2020, 20 2023 post, how important Jenkins is and how much it is used by the organizations, both existing and new organizations, perhaps. Well, that is first number we can share, perhaps, and I can continue with others, and maybe Sasha, you can add your ATE to as well. The second number we have is about the workloads.
Like all job types, like Jenkins pipelines is one way you can create your pipelines, but in Jenkins, you can do things many different way. And if you consider all those different ways and think them as workloads regardless of their type, that also shows 45% increase. So it's kind of another important data point that shows, okay, some organizations might prefer to use pipelines, but others might be doing something else regardless of what they're doing.
That shows strong growth for Jenkins when it comes to how organizations are using. And finally, and this is not an easy number to, you know, come up because some organizations may not be providing usage statistics to Jenkins community, but some, uh, report, some, uh, analyst firms estimate Jenkins market share around 40%, which is, again, a really big number because if you consider number of developers around world, 25 to 30 million, 40% of 25 to 30 million is like more than 10 million developers using Jenkins. So it's like, it's really important to think that Jenkins is maybe half of the developers they do something with Jenkins, maybe creating plugins or just continuing extend jobs, or just getting feedback from the jobs created by their colleagues.
The one way or other generally touches lives of different types of, you know, developers. So these numbers are pretty, I important to know that it still continues to go strong. I just, just to put some numbers out there on it, I, I happen to have access is, uh, you know, the Jenkins pipelines jobs as of June of 2023.
So just a month or two ago, two months ago, over 48 million jobs per month. 74 per month. I mean, those are, to put it in, in context, right?
Fred, you said to what it was it 25 million developer, something like that. It's almost three three per developer, right? For every developer in the world per month.
That's crazy. Scho, what does it mean mean to you? Yeah.
Well, those are, furthermore for me, they're just baseline numbers, right? Uh, I don't want to get too technical, but it's important to understand that a lot of the numbers, it's not everything that's happening in Jenkins land. Um, if, uh, uh, you, you have to accept that your jobs that are being, uh, your, your statistics are being sent, right?
I suspect many banks are not shipping their statistics on a daily basis. Uh, you need to, um, also make sure that, uh, you run Jenkins in a quote unquote, relatively static fashion. Increasingly people are starting Jenkins, shutting it down, and, and using very dynamic way to operate.
If that's how it works, chances are very high. Those are not gonna be counted. So I think it's, it's really for the way to see those numbers, uh, is really to think about it as a, as a baseline, as a minimal amount.
But there is, it's like the tip of the iceberg. There is everything you don't see. And, uh, and, and that I think represent well, Jenkins as well, right?
Uh, we sometimes don't talk about Jenkins, even though it's in front of us. It's, it's everywhere. And as you said, 73 and change, 74 million of, of, of jobs is, is mind boggling in terms of, of number.
It's, it's, it's, it's amazing. Um, one number that, uh, you know, I hinted at that before, but we're, we're, you know, we're counting more than 600 developers contributing to the project in various capacity, can be on plugins, can be on core. And, and that is, uh, super exciting, right?
Because using open source, I, I get that right, but if nobody's contributing to open source, we all face the same problem, right? You still need to, to, to, to get new contributions. Uh, a project is, is alive, right?
You have new security issues, you have improvement. You need to bring, you have new a p i, new cloud, a p i, you need to support. And to, to imagine that you have more than 600 people willing to contribute time, uh, either as professional or as a hobbyist is, is amazing.
It's a testament to the health of the project 18 years after its birth. Absolutely. You know, if you look at, uh, so the CD Foundation, sister Foundation of course is C N C A, right?
Cloud Native Computing. And, you know, well, all of the Linux foundations, I think use this kind of sandbox, incubation, graduation sort of, uh, model. And, and, and those models are based Sasha, right?
On those kind of things. How many people are contributing, how many downloads? Ha you know, the govern, uh, the, the maintainers and, and all of these things, by any measure along that line, Jenkins is, is outsized, right?
I, I don't have numbers in front of me, but I would say that it competes favorably to the largest C N C F, uh, uh, projects such as, uh, uh, Kubernetes and not, not well, Prometheus, and then Open Telemetry. I mean, these are monster, monster, the biggest open source projects out there, right? And, and Jenkins is in that sort of class.
So, um, I mean, certainly the, the, by any stretch of that, let me ask you, you know, a lot of people a couple years ago were saying, well, with Kubernetes, speaking of Cloud native, with Kubernetes, I don't know if Jenkins is still gonna be relevant, if we're still going to use it, certainly by these numbers. It can't be that everyone in the world is using Kubernetes, but not using Jenkins. 'cause there's a lot of Jenkins going on.
So, you know, there, there seems to have been a, an evolution, if you will, where Jenkins is very much being used in cloud native environments. Yes. Yeah.
It, it's, it's, um, it's interesting because in the 18 years of, uh, of Jenkins, we've seen companies and project come and go. So it's not a criticism or I'm not being, uh, snarky here. I'm just saying that it's, it's great, uh, uh, because Jenkins really created a practice more than a project.
It defined a practice. And following that practice, a lot of innovation took place. A lot of new project, open source project, and new, a lot of companies came up with what they thought was a better way, was a different way to do things.
And all of that sometime gets lost, sometimes get your traffic in, in two other products, including Jenkins. So you have this, this, uh, uh, in-depth innovation taking place. If, uh, Jenkins is about 44% of installed base, it means that 56% are doing Jenkins and something else, or something else.
Um, and so you have different use case, different choices based on taste and colors and, and so on. But I would certainly not say that if you are doing, uh, you know, Kubernetes deployment or several less deployment or ai, then Jenkins is not for you. It covers such a broad, uh, number of use cases.
It's what makes this strength right, in, in, in some ways, some other projects can be better if you do just one thing, right? If you have one mission, one use case, maybe you can find a tool that's gonna be a better fit. But for lots of organizations, they actually do 20 different things.
They do ai, they do Kubernetes, they do the, uh, they do embedded, they do a bunch of things. And to have one system to handle all of that is actually a better option. So yeah, it's, it's very much alive and kicking.
Absolutely What such said, because another, uh, important thing to highlight about Jenkins is, is extensibility, which goes back to what she, Sasha said, like innovation. Like if you look at Jenkins plugin ecosystem, there are about 2000 plugins there. And if you search for Cloud Native, they'll get tens of different plugins.
So again, it's obviously, it's important to pick and use the right tool for the purpose, but at the same time, flexibility and a bit to, you know, go and create something and give that back to work. So others with similar needs or use case could utilize that themselves as well as an important. So it's, again, just looking at the plugin, a customer of Jenkins shows that lot of organizations are using Jenkins for cloud native type of development as well.
So I, I think it is important to highlight that the innovation and the community behind Jenkins is what enables this and helps many organizations regardless of their product structure or type of products they're developing. Agreed. Guys, we're about outta time for people who maybe want to get a little more insight into this.
Maybe they have some selling to do internally around Jenkins at their organization. Where can they get any of this? On the CD foundation website?
We will soon have, uh, this information made available on, uh, CD Foundation website, but Jenkins project has its own website as well. Jenkins dot I also, that's should be another place to look at C Foundation, the, the place to go to for, yeah, yeah. Excellent.
And, and just one thing, Alan, if you don't mind. A lot of organizations sometimes feel a bit awkward in how they get to start interacting with a project. How do I get started?
How do I maybe even contribute? Uh, how do I learn? The C D F is a great place for that, right?
You, you, you can, uh, you can find a lot of knowledge. You can, you know, a, a great way that lots of companies find is to become member of the C D F to participate in the C D F. Uh, we have Fidelity, for example, who is on the board, uh, who has a, a a a seed there.
They're doing amazing work. So we're seeing a lot of, of, uh, of passion from organization. 'cause that's a, a really good way, corporate compatible way to, to, to engage, to learn, to educate your teams, to contribute what maybe you're missing from the product, and so on and so on.
So, uh, there is a lot of value for organizations in, in participating in the C D F. Excellent, excellent, fatty Sasha, thank you so much for joining us today. You know, I'll just say this, the state of Jenkins is strong.
io. We're gonna take a break here on Techstrong. We'll be right back.