Steve Terrana - Pipeline Templating: Lessons Learned From Enabling CI/CD For Microservices
Playback access may have expired or the stream is unavailable. Reload the page to request fresh access.
Another tab is open for this lesson. You can keep watching here; the newest position wins.
Saved position may be approximate: the browser clock disagreed with the server.
Your free preview has ended
Create a free account to finish this lesson, or subscribe for the full library.
Your viewing record
No viewing recorded yet. Press play; your position is saved about every 10 seconds.
Last viewed . Last position —.
Completion
Based on 0:00 of unique watched video. Repeats and skipped parts do not increase it.
Most CI/CD tools are awesome at automating software delivery processes for a single application.
With the adoption of microservice-based application architectures becoming more and more prevalent, a gap is emerging in our available tooling.
What happens when you need to support a CI/CD pipeline for dozens of applications?
With most, if not all, CI servers this means duplicating the pipeline definition; resulting in manual onboarding steps, a lack of standardization, and a brittle CI system that is hard to scale and maintain.
One approach to addressing these problems is pipeline templating - creating tool-agnostic workflows that can be shared across applications. As the author of the Jenkins Templating Engine, this interview would explore lessons learned from implementing pipeline templating and enabling large-scale CI/CD adoption.
Topics:
-
Can you tell us what exactly you mean by pipeline templating?
-
How exactly did this idea come about?
-
What are some of the benefits of this approach?
-
What's next for the Jenkins Templating Engine?
Comments (0)
Log in to join the discussion.
No comments yet. Be the first to comment.