
Sign up to save your podcasts
Or


In episode 12 of The Pipeline: All things CI/CD & DevOps Podcast we are joined by Marky Jackson, Director of Open Source at OpsMx. As we continue to celebrate Jenkins graduation from incubating project to graduate, we are inviting community members who have contributed to Jenkins one way or another. Today we will cover what it means to be a plugin maintainer for the Jenkins community and what does that task entail. Marky will cover some tips & tricks to being a successful plugin maintainer, as well as, some personal experiences from feeling like a rockstar to dealing with some not so friendly folks from around the open source universe. Listen to learn more and how you can get involved in open source communities.
Support the show
Gather round children as today we are going to listen to the tale of Jenkins!
August is a special month at the CD Foundation - our first project is graduating from incubating to graduate status. As part of our celebration month we wanted to bring our audiences a throwback snippet of how Jenkins began and who best to tell that story none other than the creator himself, Kohsuke Kawaguchi! In this episode you will learn about how Kohsuke came up with the idea of Jenkins and how it evolved over the past 16 years!
Support the show
Summary: In this episode, we’ll discuss Continuous Updates, a concept introduced in the Liquid Software book by Fred Simon, Yoav Landman, and Baruch Sadogursky. It is a logical next step in all the things continuous, as Baruch will explain. Tune in to hear the Head of DevOps Advocacy in JFrog talking about his, JFrog’s, and even some of the industry’s DevOps Journey.
Bio: Baruch Sadogursky (a.k.a JBaruch) is the Head of DevOps Advocacy and a Developer Advocate at JFrog. His passion is speaking about technology. Well, speaking in general, but doing it about technology makes him look smart, and 19 years of hi-tech experience sure helps. When he’s not on stage (or on a plane to get there), he learns about technology, people, and how they work, or more precisely, don’t work together.
He is a co-author of the Liquid Software book, a CNCF ambassador and a passionate conference speaker on DevOps, DevSecOps, digital transformation, containers and cloud-native, artifact management and other topics, and is a regular at the industry’s most prestigious events including KubeCon, DockerCon, Devoxx, DevOps Days, OSCON, Qcon, JavaOne and many others. You can see some of his talks at jfrog.com/shownotes.
Support the show
Guest speaker: Andy Grabner
While software architects have broken their monoliths into event-driven service architectures, many pipeline architects still try to apply a monolithic pipeline approach to deliver these new architectures. This results in constantly outdated pipeline code, tight integration of process and tools, lengthy diagnostics sessions to fix broken pipelines and puts strains on the underlying resources that build, deploy, test and validate. In this workshop we introduce a new approach: Event-based Continuous Delivery which decouples the declaration of processes from tooling. It uses a “everything as code” approach which includes deployment, testing, quality gate, observability and promotion definitions. One open source project which implements this new approach is Keptn (www.keptn.sh). Listen to this episode to learn more.
Support the show
Guest Speaker: Tiffany Jachja
DevOps adoption rates have quickly risen throughout organizations that own software services. For many of these organizations looking to scale their efforts beyond pilots and one-off initiatives, they often find themselves on the curve of diminishing returns. Value stream management is a lean business process that helps organization leaders track the value of their software efforts and resources. Using value stream management practices, you can optimize your flow of materials and information by lowering costs and improving value adds. Join this podcast episode to hear shares some insights about Value Stream Management.
Support the show
Join Helen Beal today as she covers...
The origins of continuous delivery are in the agile manifesto where, in the first of twelve principles, it’s stated that the highest priority is to satisfy the customer through early and continuous delivery of valuable software. Fast forward nearly twenty years to a world subsumed by DevOps, where continuous delivery is synonymous with pipeline technology and we have an emerging market around value stream management. In this podcast, we’ll explore the relationship between all these pieces and see how they all fit together with the same ultimate goal: the improvement of organizational performance.
Support the show
In this episode, we are discussing GitOps with Viktor Farcic from CloudBees. We explored some fundamental questions:
Support the show
CDF Community Ambassador, Garima Bajpai, presents: DevOps Moonshot & Continuous Product Oriented Practice!
We have overcome the traditional technological limitation of hardware, software & applications which enables us to take up the “Moonshot Leap” towards software development, which advocates a high level of ambition, where millions of software developers will collaborate to create open source technology solutions to improve life index of people, setting new goal in organisation where teams think big and shift the perspective that through next generation “State-of-the-art” development of software anything is possible, taking a leap from continuous improvement to exponential improvement.
Get in touch with Garima:
Support the show
Dan Lorenc, Christie Wilson & Jason Hall from Google talk through and define the different terms in software delivery, including Continuous Integration, Deployment and Delivery.
Support the show
Panelist include:
Organizations often employ more than one tool in various stages of their CI/CD pipelines due to different capabilities provided by the tools and this is perhaps one of the biggest benefits users get by using open technologies for their CI/CD needs. However, one of the challenges users face is the lack of interoperability across the CI/CD tools and technologies, resulting in various issues while constructing and running pipelines such as passing metadata and artifacts between the tools or achieving traceability from commit to deployment. Often users end up building their “own glue code” to address what is a common problem, further complicating moving from one tool to another and adopting new technologies and methodologies.
These “glue code solutions” are generally specific to users’ needs and tools rather than being loosely coupled and agnostic to tooling and technology. Additionally these solutions are not visible to other users and the communities, making them vulnerable to the risk of outage in their CI/CD pipelines due to potential changes (i.e. non-backward changes to the APIs, changes in data models) that happen to the tools in respective projects.
Therefore, focusing on tool interoperability is critical. The Continuous Delivery Foundation highlighted interoperability as one of the Foundation's 9 goals. The Interoperability special interest group (SIG) was founded as the forum for driving towards this goal.
Support the show
From the publisher's feed