We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Making Continuous Delivery Accessible to All

00:00

Formal Metadata

Title
Making Continuous Delivery Accessible to All
Title of Series
Number of Parts
542
Author
License
CC Attribution 2.0 Belgium:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
New technologies such as Kubernetes and methodologies such as microservices are changing how software is developed, delivered, and deployed. Additionally, bringing new products to the hands of users is happening much faster than before, making Continuous Delivery a critical aspect of doing business. The way we do business is evolving at a tremendous pace and keeping up with the technology and tooling can often put strains on companies regardless of size or number of employees. Knowing where to start is one issue but then once you’ve started how do you scale. Do you need more tools, which tools do you need, what resources do you have to help you pick the right path to keep your company running efficiently, how do you train your developers while they continue to do their day jobs? The CD Foundation was formed and incubates projects that address these challenges in an open-source, vendor-neutral manner. Using best practices from graduated projects like Jenkins and Tekton as well as incubating projects like CDEvents and Spinnaker, the CD Foundation is working on the CD Reference Architecture to help take the guesswork out of tooling and scaling and creating a blueprint on how to establish, structure or modernise your CI/CD infrastructure. This talk will go over some examples of the CD Reference Architecture and resources available to help make CD accessible for your organisation.
Analytic continuationContinuous integrationTelecommunicationCASE <Informatik>Self-organizationTransformation (genetics)SoftwareBitCentralizer and normalizerMereologyDifferent (Kate Ryan album)Similarity (geometry)Dataflow8 (number)Digital photographyInternet forumMeeting/Interview
Continuous functionAnalytic continuationSoftware developerProjective planeSelf-organizationTerm (mathematics)Information securityDifferent (Kate Ryan album)Type theoryCurveSoftwareData structureProduct (business)Lecture/Conference
ArchitectureCASE <Informatik>Observational studyView (database)Graphical user interfaceScalabilityInformation securitySoftware developerWindowContinuous functionChannel capacityBookmark (World Wide Web)PlastikkarteSoftwareOpen sourceAnnulus (mathematics)Event horizonCumulative distribution functionGroup actionElectronic mailing listAnalytic continuationProduct (business)Event horizonDifferent (Kate Ryan album)Projective planeQR codeComputing platformMereologyOpen sourceSelf-organizationTrailGroup actionFigurate numberFeedbackComplete metric spaceBuildingSpeech synthesisSoftwareType theoryVelocityDigital rights managementCASE <Informatik>MathematicsMultiplication signSoftware frameworkWeb pagePhysical systemPlug-in (computing)Right angleOnline helpIntegrated development environmentPoint cloudDisk read-and-write headPublic domainMedical imagingOpen setPresentation of a groupWordVirtual machineBoundary value problemConfidence intervalChainInheritance (object-oriented programming)Operator (mathematics)ScalabilityQuicksortSoftware developerBoom (sailing)Scaling (geometry)Slide ruleOrder (biology)Latent heatEmailComputer programRevision controlServer (computing)DatabaseGoodness of fitComputer animation
Event horizonSoftware developerProjective planeData conversionWebsiteOnline helpMultiplication signAnalytic continuationInformationLaptopSuite (music)Self-organizationProcess (computing)Knowledge baseDifferent (Kate Ryan album)CollaborationismLecture/Conference
Computer fileBookmark (World Wide Web)View (database)WindowOpen setTouchscreenOrder (biology)Computer animation
WindowWorld Wide Web ConsortiumOnline helpGraphical user interfaceComputer fileView (database)Bookmark (World Wide Web)Program flowchart
Transcript: English(auto-generated)
Thank you very much, I am very happy that you are here, it is very nice to meet you, it is very nice to meet you, it is very nice to meet you.
Welcome everyone, thanks for being in the CIC day room and thanks to CIC day room moderators for organizing this event.
So, Laurie, would you like to go first, talk about who we are and so on. Okay, so my name is Laura DeRusso, I work for JFrog, I am the CDF's marketing outreach chair and I am also the chair of CDCon which is May 8th and 9th this year in Vancouver. That is a picture of me and my kid, that is Instagram because we look like we are
happy but we had just gotten lost in Central Park, so you know, don't always believe what you see. Thanks Laurie, my name is Fahid Tirmens and I work at the Linux Foundation as the executive director of the Continental Foundation and I have seen Laurie's photo, so I had to put my photo with my son, so he is my son, 7 years old
and we are actually, we are not lost, we are enjoying the, what is that rotating wheel, that thing, so it is in Ireland. So, today we want to talk about a topic which we have been talking a lot about last couple of years.
So, as you see, we have all these different industries, finance, healthcare, telecom and if we think about these different industries, the continuous integration and continuous delivery deployment, it is common of all the industries regardless of what they are doing. So, all these industries have certain needs and requirements when it comes to developing
their products, getting them tested, getting them delivered and made available to their end users. And sometimes, when we talk about continuous integration and continuous delivery, we focus around tools and technologies.
Yes, tools and technologies are really important, that is what enables us to establish new pipelines, run end-to-end software flows and get the software out there to field. But when we think about what actually continuous integration and continuous delivery means, that part is a bit tricky because everyone has their own concerns, everyone has their own use
case and when you talk to certain individual or certain organization, they come up with different things because the way the organization's communities embrace continuous integration and continuous delivery differs from each other.
Some of the organizations have been doing continuous delivery for years, they are very mature, they know what they need next and some of the organizations are a bit slower compared to the others and they are just starting their continuous delivery transformation, for example. And I actually remember, I think it was three or four years ago, it was this room if I am not mistaken, I was talking about similar topic for telecom industry.
And telecom industry, as you know, it has been like very coupled, you know, property, hardware, software and so on, and telecom industry is going through this transformation and it is taking a while for telecom industry to actually embrace the continuous delivery. And because of that, we need to make sure that we put the individuals, we put
the organizations, we need to put the communities together to make sure we can collaborate across different industries, across different projects and different communities to find out how we can best help each other and make sure everyone moves forward while they transform their business or communities for continuous delivery.
So, I am sure all of you know what continuous delivery is. Continuous delivery is a software development practice enabling organizations to deliver software with speed and security as well as sustainability and other things. And it has become really important for, again as I said, organizations regardless of the size, type, industry and so on.
And without continuous delivery, it may be challenging to push the new software out there. But if you go back to what I was just talking, and this is typical innovation adoption curve. And if you think about different organizations, different companies, different communities, some of them are ahead of others.
Like if you think about Silicon Valley companies, they have been doing continuous delivery for years, decades even. Like when it was first, this term was first coined continuous integration, 90s being of 2000s. And they came forward a lot. So those organizations, they have lots to share with others who may be just starting.
And we have some organizations in between, they already started working with continuous delivery, but they are trying to find out how to find out what is next to do. So if you think on the organizations that are ahead of their peers, for example, they adopted continuous delivery years ago.
They are trying to find out what else they need to do. They are thinking about different topics. But if we think about the other end of the curve, those organizations may not be interested at all.
They may think they are different from the other companies. They are different from other organizations. And they may say, oh, our product structure is not like that. We can't apply continuous delivery to what we are doing. So we don't need this. And in between, different types of organizations doing different things.
And that is where we see the actual need to collaborate broadly. Because, again, if we look at the adoption curve, the organizations that are ahead of others, they are thinking about some really hard questions. They are trying to find answers to those questions like security, scalability, and sustainability.
Like when you start your continuous delivery of pipelines, you start simple. Your pipelines don't cross organizational boundaries. You may have one CI server that may be enough for your organization. But when the scale comes in, then things start happening. And how to make sure that your pipelines passing through multiple organizational boundaries could be established,
providing feedback to different parts of organizations, from developers to sales teams, for example. And those organizations are looking at scalability aspects, interoperability aspects. They need somewhere to work with these topics. And they need somewhere to share their experience with others.
And the other group of people might be looking at developer productivity and experience. Because they have done with continuous delivery, it is working fine. But their experience of their developers are suffering. So they need to fix that. And if you think other types of organizations, they may be after standardization. Because everything is working fine, but all the teams in the organization are doing things in a different way.
And it is very costly and time consuming to maintain those things, for example. And finally, some organizations may be opposing the idea of continuous delivery because their products are different. And they don't believe in continuous delivery. And they may need help talking about best practices, white papers, and so on.
And this is the key thing to make sure that, okay, as I mentioned, tools and technology, it is important. But more important than that is to come together and share all these learnings, challenges, concerns, use case with others. So we can learn from each other and push domain forward together.
Okay. So the name of this presentation is Making CD Accessible for All. And so we are with the Continuous Delivery Foundation. So who here is a part of the CDF? Nobody? So this room is the CI CD room and we don't have one hand going up.
One hand! Yes! Two! Okay. So the CD Foundation was brought together to help solve these challenges. It's a vendor neutral organization under the Linux Foundation. And we're here to make things work better. So where do you find us? So get your phones out. I know everybody likes phones and likes to take pictures of slides.
I am QR code heavy in this presentation. So the first thing you're going to want to do is go to... Stop! Terrible! Bad, Fatih, bad! Okay. So the first thing you want to do is to check out our website, right? So that's got all of our information on it. It's got our projects. It's got where to find us. Blah, blah, blah.
But if you want to get right into the conversation, go ahead and join our Slack channel. Yes, I know. Another Slack channel. But that's okay because this one is alive and it's well. And people are on there commenting, asking questions. The SIGs, the working groups, the projects are on there. And it's your best resource to find out what's going on in the CDF,
what people are currently looking for, and where maybe you can contribute. And then when I come back next year and ask how many people know about the CDF and are in the CDF, y'all are going to raise your hands. It's going to be amazing. Okay. Challenge! So if you didn't know, the CDF has nine projects. And ooh, I need my notes. Hold on.
Our first project is probably our most well-known project, which is Jenkins, and it graduated. And so I'm just going to give you some, like, a commercial for each of these so that you can kind of go back and see if these are things that you currently use or maybe want to look into. So Jenkins is the leading source open automation server, providing hundreds of plug-ins to support building, deploying, and automating any project.
And when I say that it's graduated, that means it was incubated within the CDF and then it became sustainable on its own, and it's then moved out. So we still do everything with Jenkins. They're here. They're upstairs. They're building K. Go check them out. They've got lots of good stuff going on. The next one I want to talk about is, these are all in just crazy order,
Spinnaker, which is an open source, multi-cloud, continuous delivery platform for releasing software changes in high velocity and confidence. Then Screwdriver, so I've got them in, like, the order in which they came into the CDF. This is just picture order. Let's just not pay attention. So Screwdriver, it's an open source build platform that facilitates the workflow for continuous delivery pipelines.
Then we have our little alien, Ortilius, which is all about microservice tracking. And then we've got Jenkins X, and that is a CI CD for Kubernetes with preview environments on pull requests using cloud native pipelines from Tekton. Tekton Pipelines is on there, which also graduated recently.
It graduated last October, and so it's an open source framework for creating CI CD systems. Shipwright is a framework for building container images on Kubernetes. CD Events was born out of a SIG, and this is one of our newest incubating projects, and they are in version 0.1 right now, with 0.2 about to come out,
which is a very exciting project if you're looking for something in the events space. So CD Events are a common specification for continuous delivery events, enabling interoperability in the complete software production ecosystem. They've got a lot of cool things. They're working to integrate with other projects that we have. Oh, Jean-Marc for Jenkins. Stand up. There's our Jenkins guy right there.
He runs Google Summer of Code for Jenkins. We love him. He's amazing. And then our last project that just got entered into the CDF is Persea, and it's creating a decentralized package management network. So we don't like to use the word blockchain, but we'll use the word blockchain. You know, an immutable ledger, all that good stuff, so you can track and see where everything was built.
All right, phones out. So special interest groups, right? So if you're like, I'm not ready to join a project, but what else is going on within the CDF? So we have currently five special interest groups. Best practices, interoperability, events, software supply chain, and MO ops.
So as Fatih was saying earlier, like, best practices. What are you doing? How did you scale? How did you get there? What are you using? What tools are you using? What size is your company? My company is going to be that size. How do I get there in the easiest way possible? Boom. Best practices SIG, that's what they're trying to figure out. Interoperability, this one has got a lot of, like, spiciness happening right now.
This is sort of, like, a big buzzword, and they are working hard. This is one of the most active groups that we have. And so they are trying to figure out, like, interoperability with an ecosystem. Like, how do you track events? How do you see what's going on? And how do you make all your tools work together? So if something breaks, you get notified. Shaking your head. It's fine. So next is our events SIG, and again, CD events came out of this SIG.
So they realized it was more than just a SIG, and they wanted to create a project. We have a white paper. They're, like I said, it's in the back? Yes. So there's a white paper in the back. You can learn about it today. And they're about to release their next version, and it's very exciting.
We've got some big companies working on it. And again, the thing about the CDF is that it's vendor neutral. So we've got companies like Netflix, eBay, Google, Amazon, just huge corporations that are working to solve this problem collectively, which I think is super important so that we're all on the same page moving forward. Software supply chain. We've all heard about software supply chain attacks.
It's gone up 742% in the last year. So this is something that's super important. And again, just like a lot of other groups, we're out there trying to figure out the best way to secure pipelines. And lastly, MLOps, it's machine learning, bringing what's learned in the database and the science side over to methodology and trying to move forward in a good, practical manner.
So five minutes, so we're good. So we would love for you to join us and help build out the future of continuous delivery. We've got end users. We've got vendors. We've got projects. The whole thing is we're working together to solve the problems. And if you want to join our mailing list, that's another QR code.
And I know I said this earlier, but if you're interested in talking at CD Con, which is in Vancouver, it's combined with Open Source Summit NA and GitOps Con. Our CFP is open until next Friday. I'm program chair. I would love to read your abstracts
and get you all on the speaking slot. That would be amazing. And that's our session. Any questions? We've got five minutes for questions or no questions.
Awesome. I do have one question. How much time do we need to participate in the CDF? So it's volunteer only, right? So you determine how much time you want to volunteer. As marketing chair, I volunteer a lot of hours, but I work for a company that allows me to work in open source, which is really cool.
But I also do stuff on my own during my downtime. One of the things I love about working in the developer community is that you guys just love developing on your off time, during your work time, like when you're on vacation, I see you with laptops at the pool. So my suggestion is just check out what we have to offer and see if it's something that interests you.
There's nothing wrong with striking up a conversation with somebody online to see, is this worth it? Is this really an active group? I think that's what we find out a lot about communities that we join. Sometimes they're active, sometimes they're dead. But just give us a shot and I think you'll be happy. Yes?
I'll take that question. I know. I could have said it even further away. How do you see the adoption of CD events in projects outside of the CD Foundation? Okay, so the CD events project is getting contributions
from projects outside of CD Foundation, such as Captain. I don't know if any of you have heard Captain, which is like event-based control, playing for continuous delivery, which is a project at CDF. Sorry, CNCF, right, yeah, CNCF. So that kind of collaboration is happening, but the main thing that slowed the CD events adoption
was not having a release. So as Laurie mentioned, the project made their first release like a month or two ago, 0.1, and they are working on getting CD events adopted to two CDF projects, and I am sure the other projects outside of CDF will follow the suit.
So currently the discussion is around Jenkins and Spinnaker adopting CD events. So once they adopt, then others will hopefully follow that outside of CDF. So do you produce any documentation for people or small organizations
who want to use CI processes or to start using them to overcome common issues? Yeah, the best practices...
Okay, the question was if we have any documentation to help organizations with different sizes, like small size startups or large size. Was that correct? So the best practices SIG actually developed a website which is called bestpractices.cd.foundation,
and on that website you can find such information how to start with continuous delivery regardless of your size or what you should be looking at depending on the size of your company. And that document or that website is collectively developed knowledge base so you can look at it and if you find something missing there,
then you can go and contribute and improve the documentation. So just go to the website bestpractices.cd.foundation and you have the entire website for that. And thank you. We are out of time.
It's muted. I think our mute is on. Okay, next one.
All right.
So one last thing in order to stay in the middle of the screen.