I've searched the web and not come up with a good answer to this, but for some reason (after upgrading to TortoiseSVN 1.9.0?) my Subversion revision log file format has changed, which is confusing the Jenkins SVN plugin, and I am confused as to why.
In .../Repository/db/revs/0, looking at the tail of the revision files I get the following for tail -n40 116, an older revision:
PLAIN
K 8
branches
[elided]
ub-3.0.t115-38 modify-file true false /trunk/foo/bar.c
17579 17721
For tail -n21 117, the HEAD revision:
DELTA 116 17463 103
SVNgfK▒a19
[elided]
ua-3.0.t116-39 modify-file true false /trunk/baz/wibble.h
4646 4785
Is there some tool to convert these DELTA revision logs to PLAIN format, or some setting to prevent DELTA revisions being created?
UPDATE: This problem this is appears to be causing is described in this bug report.
Here is the full answer that has worked for me.
First, following this guide, and assuming /cygdrive/c/SVNRepository as the repo location, do the following to take a snapshot of the current repository:
cd /cygdrive/c
svnadmin dump SVNRepository/ >copy.dump
rm -rf SVNRepository
svnadmin create --compatible-version 1.8 SVNRepository
Note that the --compatible-version 1.8 is very important as Jenkins cannot yet understand the new 1.9 format.
Now using an editor of your choice, load up SVNRepository/db/fsfs.conf, eg:
vi SVNRepository/db/fsfs.conf
Find the following two lines (lines 61 and 69 for me):
# enable-dir-deltification = true
# enable-props-deltification = true
And change them to:
enable-dir-deltification = false
enable-props-deltification = false
Now import the snapshot into the fresh database:
svnadmin load SVNRepository/ < copy.dump
Now, Jenkins should be back working again!