Geo - Recalculates the checksum for projects up to date
What does this MR do?
Fixes possible race condition when calculating repositories/wikis checksum.
Why was this MR needed?
Successive pushes in a short window can lead to a race condition: first job calculates the checksum, second one doesn’t run because the checksum isn’t cleared.
Does this MR meet the acceptance criteria?
-
Changelog entry added, if necessary -
Documentation created/updated -
API support added -
Tests added for this feature/bug - Conform by the code review guidelines
-
Has been reviewed by a UX Designer -
Has been reviewed by a Frontend maintainer -
Has been reviewed by a Backend maintainer~~ -
Has been reviewed by a Database specialist
-
-
EE specific content should be in the top level /ee
folder -
Conform by the merge request performance guides -
Conform by the style guides -
If you have multiple commits, please combine them into a few logically organized commits by squashing them -
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-and-qa
manual pipeline job)
What are the relevant issue numbers?
Closes #6773 (closed)
Closes #6423 (closed)
Edited by Douglas Barbosa Alexandre