Skip to content

Rename project's pipelines relation

Francisco Javier López (ex-Gitlab) requested to merge fj-rename-project-pipelines-relationship into master

What does this MR do?

We are using pipelines for different purposes not just CI, for example chatops or the web ide. The problem is that all these pipelines are displayed in merge requests, commits, and they're not as important as the CI are. For example, if we commit something to an MR, and then we open a web ide terminal in that MR, what we expect to see in the MR page is the CI pipeline status of the commit, not the web ide terminal one.

Right now, we don't have a clear approach to distinguish between pipelines.

This MR split the project's :pipelines relationship into two:

  • all_pipelines: which shows all project pipelines, no matter the type, source or config_source
  • ci_pipelines: which only shows those pipelines whose config_source is :repository_source, :auto_devops_source, or :unknown_source

The MR also modifies a little bit the behavior of the import/export. Because we can't just bump the version of the backup files, we need to do it in a couple of releases. In this MR, we allow exported files with both ci_pipelines and pipelines as relationships. The resulted exported file we'll have both relationships to allow backward compatibility.

What are the relevant issue numbers?

Does this MR meet the acceptance criteria?

Edited by Ash McKenzie

Merge request reports