I recently have been working on single pipelines. The idea behind it is that with the growth of software development and the increase in how we manage, write and maintain our software and out infrastructure as separate items, there are a lot of complications that come out when integrating both in people and processes.
A regular setup when imagining software projects appears to be that despite the dream of DevOps making software teams more interoperable, they have potentially become more divided. Generally I often see teams that are separated as such:
I remember discussing some time ago about finding Unicorns where you look for people who have all of these skills, which as the suggestions of Unicorns may assume is almost impossible.
The aim of the single pipeline is that you can build the whole product in a single pipeline. In the demo shown below we deploy:
What we start to get when this is achieved not only is the essence of the product team working together, but also that each member has visibility and transparency to the workings of others allowing a greater amount of understanding, communication and collaboration over the whole product lifecycle.