www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tilman Hausherr <THaush...@t-online.de>
Subject sonarqube build failed
Date Sun, 10 May 2015 10:16:53 GMT
The SonarQube build for PDFBox has failed:

https://analysis.apache.org/jenkins/job/pdfbox/676/console
Started by an SCM change
Building in workspace 
/x1/jenkins/jenkins-master/jenkins-home/jobs/pdfbox/workspace
Updating http://svn.apache.org/repos/asf/pdfbox/trunk at revision 
'2015-05-10T08:39:46.229 +0000'
ERROR: Failed to update http://svn.apache.org/repos/asf/pdfbox/trunk
org.tmatesoft.svn.core.SVNException: svn: E204899: Cannot read from 
'/x1/jenkins/jenkins-master/jenkins-home/jobs/pdfbox/workspace/preflight-app/.svn/text-base/pom.xml.svn-base':

/x1/jenkins/jenkins-master/jenkins-home/jobs/pdfbox/workspace/preflight-app/.svn/text-base/pom.xml.svn-base

(No such file or directory)
     at 
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
...


A look at
https://analysis.apache.org/jenkins/
shows that quite a lot of builds are failing, although for different 
reasons. Wouldn't it make sense to send a mail to the appropriate dev@ 
list for a failed build, like it is done for the normal jenkins build? 
Maybe some of the projects are no longer interested in the build anyway.

Tilman

Mime
View raw message