On Wed, Apr 24, 2019 at 11:51 AM Marlow, Andrew
<Andrew.Marlow_at_fisglobal.com> wrote:
>
> Sorry everyone, I mis-spoke below. While looking at this issue I was also filing a bug report on the maven jar signing plugin, which also has a problem when the network is flaky. That is the thing that was calling out to the timestamp server, not svn. I got mixed up, sorry.
>
> Regarding the comment that was made, I don't know exactly how the svn repo is hosted in the corporate environment I am in. It is accessed via an http URL (not https, I know). The underlying filesystem is Windows because every now and then we get aggro due to the case preserving behaviour of the Windows filesystem. But is it on a network share? Not sure, but I don't think so. IMO that would be an extremely bad setup.
>
The network share Stefan and I are referring to is not on the server
side (which is accessed via https, that's fine; and we're not
concerned with how that server is set up). We're talking about the
client-side location where you're putting your working copy. I'm not
sure you fully understand the difference between "repository"
(server-side, single source of truth of the entire history) and
"working copy" (client-side checkout, where you perform local work to
perform commits from, and "update" to get other's changes). See [1]
for some more explanation.
Where are you checking out your software? Is it on a local disk? Or on
a CIFS mounted filesystem (Windows) or on an NFS-mounted filesystem,
or SMB, ... if you're on Solaris?
For example, are you doing the following?
1) Log into your Windows pc.
2) cd \\some\network\share (or cd M:\subdir; where M: is a mapped
network drive) <- this is where you're putting your working copy
3) svn checkout https://svnserver.example.com/path/to/repo <- this is
the URL to the repository, which can be hosted on Windows, Solaris,
Linux, ... whatever
If in step 2 you're indeed using some network share as the location
for your working copy, that could be problematic. As Stefan said, this
is discouraged, and you should try to put working copies on local
disks. And if you really must work with networked filesystems for your
working copy, you should look at the configuration options in the
[working-copy] section of the client-side configuration file "config"
(see [2] for some general information about the client-side config
files). Maybe some tweaks there can help.
[1] http://svnbook.red-bean.com/nightly/en/svn.basic.version-control-basics.html
[2] http://svnbook.red-bean.com/nightly/en/svn.advanced.confarea.html
--
Johan
Received on 2019-04-24 12:30:02 CEST