Automated pipelines have become an integral part of our daily workflow. As the pipelines become increasingly important, the demands placed on them rise proportionally.
As with many things, a great pipeline operates seamlessly in the background, while a poorly designed one becomes a constant irritation. But what makes a pipeline great? In what order should you run your test suites? Should you have one pipeline or ten?
In this talk, Daniel answers these questions and more by bringing up a few antipatterns he has encountered during his work as a consultant, explaining why he considers them such and what you should do instead.
After listening to this talk, you will have a better understanding of what makes a pipeline great and concrete things you can do to improve it and shorten the feedback loop.
If you missed it or simply want to relive it, you can watch Pipeline patterns and antipatterns: Things your pipeline should (not) do on YouTube.