Resolve "Geo: BaseSyncService should prune the @geo-temporary directory before fetching"
What does this MR do?
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
-
-
EE specific content should be in the top level /ee
folder -
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?
Closes #5841 (closed)
Merge request reports
Activity
@nick.thomas Assigning directly to you as this is a quick fix
Both failures are unrelated. https://gitlab.com/gitlab-org/gitlab-ee/-/jobs/66066856 is from master, this one https://gitlab.com/gitlab-org/gitlab-ee/-/jobs/66076779 fails in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/5540 too.
Edited by Valery Sizovchanged milestone to %10.7
Thanks for cleaning up after me @vsizov! Good fix.
mentioned in commit 0b286515
mentioned in issue gitlab-org/release/tasks#197 (closed)
mentioned in issue gitlab-com/migration#338 (closed)
mentioned in commit be8a5ac3
There are a few conflicts while picking this, @vsizov can you please help me fix them in: https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/5757
mentioned in merge request !5757 (merged)
Picked into https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/5757, will merge into
10-7-stable-ee
ready for10.7.4-ee
added devopssystems groupgeo labels
added Enterprise Edition label