Test engineers write a lot of code to support their testing activities. However, this code tends to be not very clean or testable itself. It creates lots of fraction and prevents Test engineers from doing their best.

While it may be relatively straightforward how Test Automation code can be done clean, tested and testable, Continuous Delivery code organization is less obvious.

Let's us hear the story about reimplementing a very complex and obscure Jenkins Continuous Delivery Pipeline code in a clean way and find what may be the general principles of making a Clean Infrastructure.