[tei-council] Jenkins build problems

[Martin Holmes]

Hi all,

Just alerting everyone to the fact that both our Jenkins machines have 
been suffering connectivity problems to the SourceForge repository over 
the last couple of weeks, and right now the problem is acute. If you 
commit a change to SVN and a subsequent build fails, look at the email 
you get (or the console output from the build job on the server). If you 
see something like this:

[quote]
See <http://teijenkins.hcmc.uvic.ca/job/TEIP5/1210/>

------------------------------------------
Started by user Martin Holmes
Building in workspace <http://teijenkins.hcmc.uvic.ca/job/TEIP5/ws/>
Updating svn://svn.code.sf.net/p/tei/code/trunk/P5 at revision 
'2014-02-03T08:47:06.187 -0800'
ERROR: Failed to update svn://svn.code.sf.net/p/tei/code/trunk/P5
org.tmatesoft.svn.core.SVNException: svn: E210004: Handshake failed, 
received: ' 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
                                      '
	at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
[/quote]

then it wasn't your fault; it was Jenkins and SourceForge failing to 
communicate properly during the SVN update process. Sebastian and I will 
typically notice this fairly quickly (assuming we're not asleep) and 
kick off the build process again manually, and we then keep trying until 
it works.

We're trying to figure out what causes this; it used to be occasional, 
but now it's happening more often than not. Meanwhile, if you do svn 
updates, exports or commits that experience connectivity problems, 
please let us know. We'd like to figure out whether the issue is with 
SourceForge SVN generally, or whether it's specific to the Jenkins 
plugin that talks to the SF SVN.

Cheers,
Martin