In Bitbucket 6.5.0 a new webhook was introduced: repo:mirror_synchronized. This webhook is triggered when a mirror has finished synchronizing with the upstream server. Mirrors subscribe to all repo:* events, but do not understand how to handle repo:mirror_synchronized and will therefore return a 400 Bad Request response to the upstream server when it tries to publish this event.
The upstream server has a circuit breaker for webhooks, which opens if a webhook fails too often. Since this circuit breaker opens for all repo:* events, even legitimate events, such as repo:refs_updated will not be published, and therefore the mirror will not receive any further events that would trigger it to synchronize with the upstream server.
Bitbucket Server 6.5.0
- Upgrade upstream server to Bitbucket 6.5.0
- Perform pushes to mirrored repositories frequently
- Mirror is updated within seconds after a push on the upstream server
- After a few pushes, the mirror stops synchronizing for up to 15 minutes, when a full sync is started.
The below exception is thrown in the atlassian-bitbucket.log file:
Currently there is no known workaround for this behavior. A workaround will be added here when available