EE: Add a new rake task `rake gitlab:traces:migrate` for legacy file trace migration
What does this MR do?
CE: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/16979 EE: here
Are there points in the code the reviewer needs to double check?
Why was this MR needed?
Screenshots (if relevant)
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated - [-] API support added
-
Tests added for this feature/bug - Review
- [-] Has been reviewed by UX
- [-] Has been reviewed by Frontend
-
Has been reviewed by Backend - [-] Has been reviewed by Database
-
Conform by the merge request performance guides -
Conform by the style guides -
Squashed related commits together - [-] Internationalization required/considered
- [-] If paid feature, have we considered GitLab.com plan and how it works for groups and is there a design for promoting it to users who aren't on the correct plan
-
End-to-end tests pass ( package-qa
manual pipeline job)
What are the relevant issue numbers?
Close https://gitlab.com/gitlab-org/gitlab-ee/issues/4639 Close https://gitlab.com/gitlab-org/gitlab-ee/issues/4170
Edited by Shinya Maeda