docs: Add warning about JUnit test reports
What does this MR do?
Customer (internal link) migrated their self-hosted instance from Omnibus to Helm, and as a result of investigation in a ticket (internal) it was found that thousands of junit test artifacts hadn't migrated as part of the procedure.
This is because the migrate script does not yet support these artifacts (and possibly some others.)
Documentation revision ensures that customers can make an informed decision about proceeding.
Related issues
gitlab-org/gitlab#27698 (closed)
Author's checklist
-
Follow the Documentation Guidelines and Style Guide. -
If applicable, update the permissions table. -
Link docs to and from the higher-level index page, plus other related docs where helpful. -
Apply the documentation label.
Review checklist
All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.
1. Primary Reviewer
-
Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.
2. Technical Writer
-
Optional: Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
3. Maintainer
-
Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review. -
Ensure a release milestone is set. -
If there has not been a technical writer review, create an issue for one using the Doc Review template.
Edited by 🤖 GitLab Bot 🤖