Do you often look at example CD pipelines and think "If only our process were that simple"? Do you need to separately build multiple modules / components and then assemble them into a release? Does your unit of release need to contain more than just a single application? Are these delivered by multiple teams? How do you go about assembling these parts and then putting them through a pipeline to validate and deploy the whole assembly? And what about version numbers - do you version the components? Do you version the whole stack at release time? How should you go about implementing these requirements? In this session I will show a typical Fan-In pattern.

I will show how you can use Jenkins pipelines to build component and assembly pipelines. I will also show various techniques for managing the assembly manifest and triggering assembly pipelines on demand, on schedule and via upstream triggers.