Revamp Multi-Project and Parent-child pipeline pages
Problem to solve
Multi-project pipelines and Parent-child pipelines are very similar, and have a lot of overlapping features. This overlap means that the parent-child pipelines page sometimes links back to the multi-project page (which existed first) with essentially a "Works the same as multi-projects pipelines" comment or crosslink. For example: https://gitlab.com/gitlab-org/gitlab/-/blob/7207b531267fe90590c47269e2811a7b745c5296/doc/ci/pipelines/parent_child_pipelines.md?plain=1#L217-L218
We also sometimes receive contributions proposing examples in the parent and child pipeline page that are already covered by the multi-project pipelines page.
We should combine them both into a Downstream pipelines page, and we can call out any differences in behavior as needed. The overall volume of content should be much shorter when combined together with CTRT topic types.
Examples
Some examples of content that applies to both types of pipelines:
- https://docs.gitlab.com/ee/ci/pipelines/multi_project_pipelines.html#trigger-job-configuration-limitations
- https://docs.gitlab.com/ee/ci/pipelines/multi_project_pipelines.html#pass-cicd-variables-to-a-downstream-pipeline-by-using-the-variables-keyword
- https://docs.gitlab.com/ee/ci/pipelines/multi_project_pipelines.html#pass-cicd-variables-to-a-downstream-pipeline-by-using-variable-inheritance
- https://docs.gitlab.com/ee/ci/pipelines/parent_child_pipelines.html#pass-cicd-variables-to-a-child-pipeline
- https://docs.gitlab.com/ee/ci/pipelines/multi_project_pipelines.html#retry-or-cancel-multi-project-pipelines
- https://docs.gitlab.com/ee/ci/pipelines/parent_child_pipelines.html#retry-or-cancel-child-pipelines
Content that is very similar, and can easily be combined by noting any differences:
- https://docs.gitlab.com/ee/ci/pipelines/multi_project_pipelines.html#use-rules-or-onlyexcept-with-multi-project-pipelines
- https://docs.gitlab.com/ee/ci/pipelines/parent_child_pipelines.html#merge-request-child-pipelines
Notes:
-
Be sure to update all links, for example: https://gitlab.com/gitlab-org/gitlab/-/blob/d7c69f3c5ca0eebb6c063588567ce8993a128f9e/.gitlab/ci/review.gitlab-ci.yml#L66
Other links/references
- Related to technical-writing#579 (closed)