On 2025-01-09 15:20, Johan Corveleyn wrote:
On Thu, Jan 9, 2025 at 1:26 PM Daniel Sahlberg
<daniel.l.sahlb...@gmail.com> wrote:
...
The only solution that will make sure you actually have a working sync is to
monitor that the sync script completes without errors. Maybe you could have a
script that looks for the svn:sync-lock property (something like svn proplist
-v --revprop -r0 http://remote.server.tld/svn/repo) at a time when the sync
SHOULD have completed?
Or perhaps try to run some daily / weekly "verification" script that
runs "svnlook youngest %PATH_TO_REPO%" or "svnadmin info
%PATH_TO_REPO%" on both sides and compares the results (or simply
mails them to you as a first step).
Yes, in addition to firing the post-commit hook add some out-of-band
monitoring. Start with svnlook, and give each revision a timeout to
appear globally. I built this quite a while ago, you can make it pretty
if you want:
https://drive.google.com/file/d/0BwYZXCxg9LJablJTQVBlSnhyeHc/view?usp=sharing&resourcekey=0-eAzfrm96zroYAwjIWt44zg
Unfortunately the code is lost in time. This was a three site
replication with transparent write-through proxying:
https://drive.google.com/file/d/0BwYZXCxg9LJaWVpwRTRqVTdtQWM/view?usp=sharing&resourcekey=0-q13rpE749tkcf3w5eHwL3A
Andreas
