Skip to content

Post Receive after lock

Georges Racinet requested to merge topic/default/post-receive-after-lock into branch/default

As experienced with #505, any write initiated synchronously from the Rails app while taking the post-receive internal API request was blocked because the locks were not released yet.

Even in the case of Merge Request creation, forwarding more information through the various layers would have been too intrusive, and more such writes could appear in the future.

This MR publishes two topics: the one on the stable branch switches post-receive to after locks release for MR auto-creation only, while it's done systematically on the default branch (currently for Heptapod 0.23.0 rc)

Merge request reports