Provide reference pipeline documentation
@romanvalov: It's an alternative view of a project goal. It arises from a practice of working with GitLab's pipeline descriptions I've got while working on a project. The idea is that instead of attempting to develop a generic pipeline template to instantiated in adopter projects it may be more convenient to provide just a reference examples and encourage projects to copy-paste the examples and adopt with project specific edits.
The motivation is that GitLab's pipeline descriptions is a rapidly and chaotically developed project and as a result is not designed with extensibility in mind in it's core. It's great to start from the ground but any complicated scenarios require evaluating different approaches. As a result not only script stanzas suffer from extensibility limitations but
rules
andcache
are also examples.Additional arguments toward the approach could be a choice of caches vs artifacts (#55) or choice of upgrade scenario job structuring (#33 (closed)) which could be project-specific.
I also see the value in a reference pipeline and would actually prefer that one for the prod pipeline at othermo, since to mitigate connection problems to SI-Gitlab I have to copy the template over anyway, do my customizations which basically renders a template useless.
The upgrade / changelog documentation will be especially interesting here and should always cover what changes and what recommended steps are to incorporate any changes in the pipeline copy.