Clear CI pipelines and jobs in projects created from project templates
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem to solve
GitLab custom project templates enable projects to be created from custom templates. When a project is created from a template, GitLab's project import/export functionality is used. This includes the history of CI pipelines, but not build traces and artifacts.
This behaviour makes for messy pipelines/jobs pages in new projects. New projects have a full history of CI pipelines and jobs that were run in the template project repository, but none of the details. The pipelines and jobs are not relevant to the new project, and add no useful information.
Further details
This screenshot shows a project that was created from a project template, with a failed pipeline from the project template (i.e., it is not a pipeline that was run in the new project).
Drilling in to the failed job simply shows that no trace is available, because the project import/export functionality does not copy build traces and artifacts.
The pipeline is not relevant to the new project that was created from a project template, and provides no useful information. It adds noise to projects created from project templates, and may confuse developers using the created project.
Proposal
When a project is created from a project template, the pipelines/jobs from the template project should not be copied over.
What does success look like, and how can we measure that?
A project created from a project template should start with a clean pipelines page. There should not be pipelines and jobs copied from the project template.