[JIRA] [subversion-plugin] (JENKINS-27231) Subversion fails first revision check

20 views
Skip to first unread message

recena@gmail.com (JIRA)

unread,
Jul 6, 2015, 10:28:01 AM7/6/15
to jenkinsc...@googlegroups.com
Manuel Jesús Recena Soto started work on Bug JENKINS-27231
 
Change By: Manuel Jesús Recena Soto
Status: Open In Progress
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

recena@gmail.com (JIRA)

unread,
Jul 6, 2015, 10:28:01 AM7/6/15
to jenkinsc...@googlegroups.com
Assignee: Manuel Jesús Recena Soto

recena@gmail.com (JIRA)

unread,
Jul 6, 2015, 10:32:01 AM7/6/15
to jenkinsc...@googlegroups.com
Manuel Jesús Recena Soto commented on Bug JENKINS-27231
 
Re: Subversion fails first revision check

sachin kung I could not reproduce the bug. Could you provide a step by step process in order to reproduce the bug? Thanks in advance.

leonardo.pinho@gmail.com (JIRA)

unread,
Jul 6, 2015, 11:04:03 AM7/6/15
to jenkinsc...@googlegroups.com

I have the same issue - jenkins 1.613 - subversion plugin 2.5

recena@gmail.com (JIRA)

unread,
Jul 7, 2015, 7:37:01 AM7/7/15
to jenkinsc...@googlegroups.com

leo pinho, It would be very useful if you describe (step by step) the process to reproduce the bug.

leonardo.pinho@gmail.com (JIRA)

unread,
Jul 7, 2015, 9:44:01 AM7/7/15
to jenkinsc...@googlegroups.com

My job was migrated from hudson and I was able to fix the issue creating a new job w/ the same settings of the old one. So I believe it is related to the migration from old hudson.

recena@gmail.com (JIRA)

unread,
Jul 7, 2015, 10:15:02 AM7/7/15
to jenkinsc...@googlegroups.com

leo pinho, IMO this issue is not related to Subversion Plugin. I would like to know if sachin kung can provide more information.

stefanreppner@gmail.com (JIRA)

unread,
Aug 10, 2015, 1:00:03 AM8/10/15
to jenkinsc...@googlegroups.com

Hitting the same issue, but only sometimes so I don't know how I can exactly reproduce it. Also I did observe that the checkout of the externals is in the logs so accessing the SVN seems not to be the issue. To me it seems that producing the changelog throws an error when there is an update in the svn externals revision.

Hole '[... SVN URL HERE ...]' aus Revision -1 in Datei '[... SVN CHECKOUT LOCATION HERE ...]' 
AU        [... SVN EXTERNAL FILE HERE ...]
AU        [... SVN EXTERNAL FILE HERE ...]
AU        [... SVN EXTERNAL FILE HERE ...]
AU        [... SVN EXTERNAL FILE HERE ...]
A         [... SVN EXTERNAL FILE HERE ...]
AU        [... SVN EXTERNAL FILE HERE ...]
At revision 4934
At revision 4934
hudson.util.IOException2: revision check failed on [... SVN URL HERE ...]
	at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:196)
	at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:137)
	at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725)
	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860)
	at hudson.scm.SCM.checkout(SCM.java:485)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1282)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
	at hudson.model.Run.execute(Run.java:1741)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:381)
Caused by: org.tmatesoft.svn.core.SVNAuthenticationException: svn: E170001: Authentication required for 'UbuntuSVN1'
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:62)
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
	at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.createSaslClient(SVNSaslAuthenticator.java:318)
	at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.authenticate(SVNSaslAuthenticator.java:92)
	at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.authenticate(SVNConnection.java:198)
	at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.authenticate(SVNRepositoryImpl.java:1276)
	at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1254)
	at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:169)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118)
	at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184)
	at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45)
	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160)
	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35)
	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
	at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259)
	at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
	at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968)
	at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873)
	at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:184)
	... 12 more

Apart from the exception stack trace the logs are the same for failing and successful checkout operations.

stefanreppner@gmail.com (JIRA)

unread,
Aug 10, 2015, 1:02:01 AM8/10/15
to jenkinsc...@googlegroups.com
Stefan Steinhart edited a comment on Bug JENKINS-27231
Hitting the same issue, but only _sometimes_ so I don't know how I can exactly reproduce it. Also I did observe that the checkout of the externals is in the logs so accessing the SVN seems not to be the issue. To me it seems that producing the changelog throws an error when there is an update in the svn externals revision.

{code:java}

Hole '[... SVN URL HERE ...]' aus Revision -1 in Datei '[... SVN CHECKOUT LOCATION HERE ...]' 
AU        [... SVN EXTERNAL FILE HERE ...]
AU        [... SVN EXTERNAL FILE HERE ...]
AU        [... SVN EXTERNAL FILE HERE ...]
AU        [... SVN EXTERNAL FILE HERE ...]
A         [... SVN EXTERNAL FILE HERE ...]
AU        [... SVN EXTERNAL FILE HERE ...]
At revision 4934
At revision 4934
hudson.util.IOException2: revision check failed on [... SVN URL HERE ...]
at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:196)
at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:137)
at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860)
at hudson.scm.SCM.checkout(SCM.java:485)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1282)
at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
at hudson.model.Run.execute(Run.java:1741)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
at hudson.model.ResourceController.execute(ResourceController.java:98)
at hudson.model.Executor.run(Executor.java:381)
Caused by: org.tmatesoft.svn.core.SVNAuthenticationException: svn: E170001: Authentication required for ' UbuntuSVN1 [ ... INTERNAL SVN SERVER NAME HERE ... ] '

at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:62)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.createSaslClient(SVNSaslAuthenticator.java:318)
at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.authenticate(SVNSaslAuthenticator.java:92)
at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.authenticate(SVNConnection.java:198)
at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.authenticate(SVNRepositoryImpl.java:1276)
at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1254)
at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:169)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118)
at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45)
at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160)
at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35)
at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968)
at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873)
at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:184)
... 12 more
{code}


Apart from the exception stack trace the logs are the same for failing and successful checkout operations.


EDIT: Oh.. in the middle of the screenshot it says something about an Authentication failure... Seems like my issue can be resolved by applying the solution from JENKINS-21785

stefanreppner@gmail.com (JIRA)

unread,
Aug 10, 2015, 1:03:02 AM8/10/15
to jenkinsc...@googlegroups.com
Caused by: org.tmatesoft.svn.core.SVNAuthenticationException: svn: E170001: Authentication required for '[ ... INTERNAL SVN SERVER NAME HERE ... ]'

at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:62)
at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.createSaslClient(SVNSaslAuthenticator.java:318)
at org.tmatesoft.svn.core.internal.io.svn.sasl.SVNSaslAuthenticator.authenticate(SVNSaslAuthenticator.java:92)
at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.authenticate(SVNConnection.java:198)
at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.authenticate(SVNRepositoryImpl.java:1276)
at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.openConnection(SVNRepositoryImpl.java:1254)
at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLatestRevision(SVNRepositoryImpl.java:169)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.getRevisionNumber(SvnNgRepositoryAccess.java:118)
at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:184)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:45)
at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:160)
at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35)
at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968)
at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873)
at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:184)
... 12 more
{code}

Apart from the exception stack trace the logs are the same for failing and successful checkout operations.

EDIT: Oh.. in the middle of the  screenshot  stacktrace  it says something about an Authentication failure... Seems like my issue can be resolved by applying the solution from JENKINS-21785 . I will report back.

stefanreppner@gmail.com (JIRA)

unread,
Aug 10, 2015, 3:56:01 AM8/10/15
to jenkinsc...@googlegroups.com
EDIT: Oh.. in the middle of the stacktrace it says something about an Authentication failure... Seems like my issue can be resolved by applying the solution from JENKINS-21785. I will report back.

EDIT2: Seems like the issue is resolved by following the steps in JENKINS-21785.

recena@gmail.com (JIRA)

unread,
Aug 10, 2015, 4:09:02 AM8/10/15
to jenkinsc...@googlegroups.com

Stefan Steinhart, my recommendation is to avoid managing the working copies with Subversion CLI and Subversion Plugin simultaneously. If your job workspace is doing managed by Jenkins, use Subversion Plugin.

recena@gmail.com (JIRA)

unread,
Oct 5, 2015, 2:43:01 PM10/5/15
to jenkinsc...@googlegroups.com

It isn't clear that this be a bug. I've tried to reproduce it in a fresh environment but everything works fine.

sachin kung Do you agree if we close the ticket?

contact@robbiecargill.com (JIRA)

unread,
Oct 13, 2015, 6:20:03 AM10/13/15
to jenkinsc...@googlegroups.com

I'm experiencing this identical issue. i.e. It happens consistently on every first revision check, following a new commit to the repository. The build will succeed on every subsequent attempt.

I've spent some time trying everything I can think of to resolve this. Tried multiple versions of Jenkins and the SVN plugin. Now upgraded all to latest and still occurs.

Master
Jenkins - 1.631
OS - Ubuntu Linux
Java - 1.7.0_75
SVN Plugin - 2.5.3

Slave
Unix slave, version 2.52
OS - Mac OS X Yosemite 10.10.5
Java - 1.8.0_45

Console output of failed build:

Started by user Robbie
Building remotely on mac-mini-slave (unity ios mac unity-ios) in workspace <redacted>
Cleaning local Directory .
Checking out svn+ssh://<redacted> at revision '2015-10-12T18:31:07.755 +0100'
A         Assets
AU        Assets/TestScene.unity
<redacted>
 U        .
At revision 17 *< Will hang here for some time, until I presume the build attempt times out or is cancelled*
hudson.util.IOException2: revision check failed on svn+ssh://<redacted>
	at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:196)
	at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:123)
	at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:726)
	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:861)
	at hudson.scm.SCM.checkout(SCM.java:485)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1277)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
	at hudson.model.Run.execute(Run.java:1741)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:98)
	at hudson.model.Executor.run(Executor.java:408)
Caused by: org.tmatesoft.svn.core.SVNException: svn: E210004: Malformed network data
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
	at org.tmatesoft.svn.core.internal.io.svn.SVNReader.readChar(SVNReader.java:473)
	at org.tmatesoft.svn.core.internal.io.svn.SVNReader.skipWhiteSpace(SVNReader.java:485)
	at org.tmatesoft.svn.core.internal.io.svn.SVNReader.readTuple(SVNReader.java:287)
	at org.tmatesoft.svn.core.internal.io.svn.SVNReader.parse(SVNReader.java:241)
	at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.read(SVNConnection.java:276)
	at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.authenticate(SVNConnection.java:174)
	at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.authenticate(SVNRepositoryImpl.java:1276)
	at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.logImpl(SVNRepositoryImpl.java:728)
	at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1038)
	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181)
	at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35)
	at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
	at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259)
	at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
	at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968)
	at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873)
	at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:184)
	... 12 more
Skipped archiving because build is not successful
Publish artifacts to S3 Bucket Using S3 profile: Jenkins S3 Profile
Publish artifacts to S3 Bucket Skipping publishing on S3 because build failed
Finished: FAILURE

For successful builds:

At revision 16
no change for svn+ssh://<redacted> since the previous build
Piping unity Editor.log from /Users/jenkins/Library/Logs/Unity/Editor.log
<redacted> *(will then proceed to build successfully without issue)*
Finished: SUCCESS

contact@robbiecargill.com (JIRA)

unread,
Oct 13, 2015, 6:21:08 AM10/13/15
to jenkinsc...@googlegroups.com
Robbie Cargill edited a comment on Bug JENKINS-27231
I'm experiencing this identical issue. i.e. It happens consistently on every first revision check, following a new commit to the repository. The build will succeed on every subsequent attempt.

I've spent some time trying everything I can think of to resolve this. Tried multiple versions of Jenkins and the SVN plugin. Now upgraded all to latest and still occurs.

Master
Jenkins - 1.631
OS - Ubuntu Linux
Java - 1.7.0_75
SVN Plugin - 2.5.3

Slave
Unix slave, version 2.52
OS - Mac OS X Yosemite 10.10.5
Java - 1.8.0_45

Console output of failed build:
{code:java}

Started by user Robbie
Building remotely on mac-mini-slave (unity ios mac unity-ios) in workspace <redacted>
Cleaning local Directory .
Checking out svn+ssh:
// <redacted> at revision '2015-10-12T18:31:07.755 +0100'

A         Assets
AU        Assets/TestScene.unity
<redacted>
 U        .
At revision 17  // < Will hang here for some time, until I presume the build attempt times out or is cancelled
{code}

For successful builds:
{code:java}

At revision 16
no change for svn+ssh:
// <redacted> since the previous build

Piping unity Editor.log from /Users/jenkins/Library/Logs/Unity/Editor.log
<redacted>  //(will then proceed to build successfully without issue)
Finished: SUCCESS
{code}

contact@robbiecargill.com (JIRA)

unread,
Oct 13, 2015, 6:21:10 AM10/13/15
to jenkinsc...@googlegroups.com
Robbie Cargill edited a comment on Bug JENKINS-27231
I'm experiencing this identical issue. i.e. It happens consistently on every first revision check, following a new commit to the repository. The build will succeed on every subsequent attempt.

I've spent some time trying everything I can think of to resolve this. Tried multiple versions of Jenkins and the SVN plugin. Now upgraded all to latest and still occurs.

Master
Jenkins - 1.631
OS - Ubuntu Linux
Java - 1.7.0_75
SVN Plugin - 2.5.3

Slave
Unix slave, version 2.52
OS - Mac OS X Yosemite 10.10.5
Java - 1.8.0_45

Console output of failed build:
{code:java}
Started by user Robbie
Building remotely on mac-mini-slave (unity ios mac unity-ios) in workspace <redacted>
Cleaning local Directory .
Checking out svn+ssh://<redacted> at revision '2015-10-12T18:31:07.755 +0100'
A         Assets
AU        Assets/TestScene.unity
<redacted>
 U        .
At revision 17  *   // < Will hang here for some time, until I presume the build attempt times out or is cancelled *
<redacted>  *   // (will then proceed to build successfully without issue) *
Finished: SUCCESS
{code}

recena@gmail.com (JIRA)

unread,
Oct 13, 2015, 6:26:02 AM10/13/15
to jenkinsc...@googlegroups.com
Manuel Jesús Recena Soto resolved as Cannot Reproduce
 

I could not reproduce the bug in a fresh environment. Everything related to SVN externals and Subversion Plugin is commented here.

Status: In Progress Resolved
Resolution: Cannot Reproduce

recena@gmail.com (JIRA)

unread,
Oct 13, 2015, 6:39:01 AM10/13/15
to jenkinsc...@googlegroups.com
Manuel Jesús Recena Soto commented on Bug JENKINS-27231
 
Re: Subversion fails first revision check

Robbie Cargill Please, file a new ticket because your environment is different:

  1. There is slave node on Mac OSX
  2. You are using svn+ssh://
  3. Your exception is svn: E210004: Malformed network data

contact@robbiecargill.com (JIRA)

unread,
Oct 13, 2015, 6:57:01 AM10/13/15
to jenkinsc...@googlegroups.com

Was just away to note svn+ssh:// in case that was relevant.

Will go file that new ticket now.

arie@catchmedia.com (JIRA)

unread,
Nov 24, 2016, 9:13:05 AM11/24/16
to jenkinsc...@googlegroups.com
Arie Skliarouk reopened an issue
 

I hesitated whether to open new bug and reopen this one and decided to reopen.
I have slight env difference - subversion plugin 2.7.1, jenkins 1.622, not sure where that matters.

We have same symptoms as described above:

  • Build that follows commit - always fails, subsequent build succeeds
  • we use svn:// (don't think it matters)
  • IMPORTANT: The svn in question has extents directory with two files in it
  • IMPORTANT: The committed change is done in the extents directory

Here is the failed build output:

Started by upstream project "App3-NextGen-iOS-Build-Choose" build number 514
originally caused by:
Started by user <redacted>
[EnvInject] - Loading node environment variables.
Building remotely on jenkins-macmini2 in workspace /Users/catch/WorkDir/Refactor/iOSNextGen
Updating svn://<redacted> at revision '2016-11-24T14:06:07.486 +0200'
Fetching '<redacted>' at -1 into '/Users/catch/WorkDir/Refactor/iOSNextGen/themeValidator'
U themeValidator/validator.php
At revision 10671

At revision 10671

No changes for svn://sources.catchmedia.com/pa_clients/jukebox/jenkins/iOS3 since the previous build
hudson.util.IOException2: revision check failed on svn://sources.catchmedia.com/pa_clients/jukebox/jenkins/themeValidator
at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:208)
at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:138)
...

There are two additional failures like the one above.

My suspicion is that the SVNKit does not handle well such corner situation.
Change By: Arie Skliarouk
Resolution: Cannot Reproduce
Status: Resolved Reopened
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

daniel.blank@advantest.com (JIRA)

unread,
Mar 14, 2017, 5:01:01 AM3/14/17
to jenkinsc...@googlegroups.com
Daniel Blank commented on Bug JENKINS-27231
 
Re: Subversion fails first revision check

I also see this issue when the svn:external-definitions are pointing to HEAD and there is a change coming in from the external-repository. Are there any plans to address this issue?

Known workarounds:

a) Don't use external definitions that point to HEAD but use a dedicated revision instead

b) Use "Ignore externals" in your Subversion Modules and instead set the external-definitions up as a separate Module in the job-configuration
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages