Fix data inconsistency issue for old artifacts by moving them to a currently used path
What does this MR do?
It does migrate artifacts to the single unique path and stores that information in the database.
Migrates the data to remove the need of having hotfix (for artifacts): https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/2224.
It makes it possible to remove artifact with:
rm -rf artifacts/year_month/project_id/
The MR for traces will be delivered separately.
This migration has to run on limited data set: about 300-400 artifacts on GitLab.com.
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 -
All builds are passing
-
-
Conform by the merge request performance guides -
Conform by the style guides -
Branch has no merge conflicts with master
(if it does - rebase it please) -
Squashed related commits together
What are the relevant issue numbers?
Edited by Kamil Trzcińśki