Skip to content

Remove pipeline artifacts page

Marcel Amirault requested to merge docs-remove-pipeline-artifacts-page into master

What does this MR do?

As pointed out in the discussions around https://gitlab.com/gitlab-org/gitlab/-/issues/412765#note_1409666309, we accidentally documented a backend implementation detail (that users have no involvement with) as a feature. We need to drop this page as it was causing confusion.

The is related to test coverage visualizations, so redirecting to that page.

We also should not talk about Pipeline Artifacts either, as they are not artifacts in the same sense as Job Artifacts, which was causing a lot of confusion. As an MVC, I'm just going to call it "data", while we come up with a better term (if something better exists).

Removed from nav in gitlab-docs!3895 (merged)

Related issues

Author's checklist

If you are a GitLab team member and only adding documentation, do not add any of the following labels:

  • ~"frontend"
  • ~"backend"
  • ~"type::bug"
  • ~"database"

These labels cause the MR to be added to code verification QA issues.

Reviewer's checklist

Documentation-related MRs should be reviewed by a Technical Writer for a non-blocking review, based on Documentation Guidelines and the Style Guide.

If you aren't sure which tech writer to ask, use roulette or ask in the #docs Slack channel.

  • If the content requires it, ensure the information is reviewed by a subject matter expert.
  • Technical writer review items:
    • Ensure docs metadata is present and up-to-date.
    • Ensure the appropriate labels are added to this MR.
    • Ensure a release milestone is set.
    • If relevant to this MR, ensure content topic type principles are in use, including:
      • The headings should be something you'd do a Google search for. Instead of Default behavior, say something like Default behavior when you close an issue.
      • The headings (other than the page title) should be active. Instead of Configuring GDK, say something like Configure GDK.
      • Any task steps should be written as a numbered list.
      • If the content still needs to be edited for topic types, you can create a follow-up issue with the docs-technical-debt label.
  • Review by assigned maintainer, who can always request/require the reviews above. Maintainer's review can occur before or after a technical writer review.
Edited by Marcel Amirault

Merge request reports