pipeline process suggestion
https://docs.gitlab.com/ee/ci/merge_request_pipelines/pipelines_for_merged_results/index.html
I read through above post and saw lot of concerns that people have and the post itself mentions.
But I am more concerned how to you manage and validate the pipeline definition file changes esp in merge request pipeline.
There is a mention of running pipeline off the parent fork/branch but if there are changes in gitlab_ci.yml then that would eventually affect the pipeline after the merge in subsequent pipeline runs.
I like the idea of having pipeline as code but not satisfied with the common implementation of pipeline def in the sourcecode of proj repo.
Suggestion: For each team/group there is a dedicated pipeline repo that would contain pipeline files for all projects under that team/group.
So for any project repo if there is a corresponding pipeline definition file in the pipeline repo under the team/group level, it should run according to that definition.
This would ensure stricter control over the pipeline esp for open source projects and its possible to do separate validation on the code and pipeline.