RE: Tsvn update does not always fetch HEAD after commit

> > As mentioned, I have a setup where I work against a svnsync'ed mirror
> repo with writethrough to the master. In this environment, a branch/tag
> operation often fails if either of the options 'switch working copy to new
> branch/tag' or 'set explicit version for externals' is enabled. The branch/tag
> creation itself completes successfully, but the followup switch/property
> operation depends on the new branch/tag being present on the mirror,
> which may not be the case if svnsync is not quick enough.
> > Is it possible to have tsvn make sure that the committed revision is visible
> before performing additional operations?
>
> I think in this situation, your setup is slightly wrong. I assume you use hook
> scripts on the server to trigger the svnsync command: that command must
> not run asynchronously but the hook script has to wait until that svnsync is
> finished.
> Of course, then you might get timeout errors if the svnsync takes too long...
>

I've looked around for guidelines on whether to invoke svnsync synchronously or asynchronously, and almost every example I've found uses asynchronous invocation, including these:

http://blogs.collab.net/subversion/yesterday-at-th
http://svnbook.red-bean.com/en/1.8/svn.serverconfig.httpd.html#svn.serverconfig.httpd.extra.writethruproxy

The discussions I've seen take asynchronous invocation for granted and focus on the details of how to do it. So even if the setup might be wrong, it seems to be the most common one. I think having tsvn wait in these situations would be of help to many users.

Oddvar

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3103844

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-03-08 19:14:00 CET