Parent-Child pipeline common usage & why

What’s this issue all about?

We want to gain an understanding of how GitLab CI users are predominantly using the Parent-Child Pipeline feature, particularly whether they are always using the strategy:depend syntax which sets the parent pipeline to depend on the status of the child pipeline upon completion.

Who is the target user of the feature?

Users of GitLab CI and/or users who author .gitlab-ci.yml files.

What questions are you trying to answer?

  • What is the percentage/frequency of Parent-Child pipeline configurations use the strategy:depend syntax?
  • Should strategy:depend be the default in all P/C pipelines?
  • What is the underlying reason that users employ the strategy:depend syntax? Examples reasons we want to confirm or disprove: (1) to make the parent pipeline status reflect the status of the child pipelines; (2) to make the parent pipeline wait for the child pipeline but not necessarily to inherit the child pipeline's status.
Core questions
Additional questions

What hypotheses and/or assumptions do you have?

What decisions will you make based on the research findings?

What's the latest milestone that the research will still be useful to you?

Edited by Thao Yeager