Skip to content

build/register.json stores last_update

What does this MR do?

As per https://gitlab.com/gitlab-org/gitlab-ce/issues/21698#note_19722633 anytime last_update is stored it will be sent with the request to builds/register.json
If it gets a 201 last_update is removed (therefore not sent with the subsequent request)
if it gets a 204 last_update is stored (and will be sent on the next request)

Are there points in the code the reviewer needs to double check?

Does this MR meet the acceptance criteria?

  • Documentation created/updated
  • Tests
    • Added for this feature/bug
    • All builds are passing
  • Branch has no merge conflicts with master (if you do - rebase it please)

What are the relevant issue numbers?

https://gitlab.com/gitlab-org/gitlab-ce/issues/21698

Merge request reports