MicrosoftGreat article, j_folberth!
YAML templates do a great job in reusing pipelines, but I often encounter a problem with this approach.
Imagine the scenario:
A company uses a Core repository with pipeline templates that are reused by several projects. This Core repository is maintained by the DevOps team, but there is also an Inner Source initiative. This allows teams to develop new features and integrate them into the Core, through PR.
In this scenario, what would be the best practices in relation to Core templates testing when a dev submits a change?
There is a proposal that suggests creating pipelines using custom tasks that encapsulate the entire logic of a stage, for example. The goal of this strategy is to be able to apply unit tests to these components. What do you think of this?
How to implement consistent tests on YAML templates? Especially in cases where there are inline script codes.
