BUG: Problems with collecting changes for repository with externals

Hi all.

We have been using TC 5.0 for a few years, and are now upgrading to Enterprise version of 7.02 (we needed more builds and agents). TC has really been working very well.

However, when I now downloaded and installed 7.0.2 on a windows machine I get into problems when I create a VCS root which has externals.

I can create a vcs root which points to a subversion repository with no externals.
The checkout performs ok, no problems.

If I just change the svn adress to a repo that has externals, I get the error below.
The same repo is being used in the other (old 5.0) server where it works just fine.
If I change the checkout rule to ignore externals, it works (but I do not get everything I want...of course).

So this points to the fact that it is a rather serious bug in the 7.0.2 version of TC.

Error collecting changes for VCS repository 'AgXSpirit Trunk'
org.tmatesoft.svn.core.SVNException: svn: E160006: No such revision 11523

jetbrains.buildServer.vcs.VcsException: Error collecting changes for VCS repository 'AgXSpirit Trunk'
org.tmatesoft.svn.core.SVNException: svn: E160006: No such revision 11523
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnSupport$SvnIncludeRuleChangeCollector.collectChanges(SvnSupport.java:551)
at jetbrains.buildServer.vcs.CollectRepositoryChangesByIncludeRulesAdapter$1.collectBuildChanges(CollectRepositoryChangesByIncludeRulesAdapter.java)
at jetbrains.buildServer.vcs.VcsSupportUtil.collectBuildChanges(VcsSupportUtil.java:54)
at jetbrains.buildServer.vcs.CollectRepositoryChangesByIncludeRulesAdapter.collectChanges(CollectRepositoryChangesByIncludeRulesAdapter.java:3)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesInSingleRepository.perform(LoadChanges.java:3)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.perform(LoadChanges.java:102)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesForCheckoutRules(LoadChanges.java:90)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChanges(LoadChanges.java:118)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.run(LoadChanges.java:64)
at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader._loadChanges(VcsRootChangesLoader.java:89)
at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader.loadChanges(VcsRootChangesLoader.java:76)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.doLoadChanges(VcsChangesLoaderImpl.java:118)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.loadChangesNoLocking(VcsChangesLoaderImpl.java:115)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.loadChanges(VcsChangesLoaderImpl.java:56)
at jetbrains.buildServer.vcs.impl.VcsManagerImpl.loadChanges(VcsManagerImpl.java:386)
at jetbrains.buildServer.serverSide.impl.auth.SecuredVcsManager.loadChanges(SecuredVcsManager.java:89)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$1.run(VcsModificationChecker.java:25)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: org.tmatesoft.svn.core.SVNException: svn: E160006: No such revision 11523
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.handleFailureStatus(SVNReader.java:269)
at org.tmatesoft.svn.core.internal.io.svn.SVNReader.parse(SVNReader.java:248)
at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.read(SVNConnection.java:268)
at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.read(SVNRepositoryImpl.java:1290)
at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLocationsImpl(SVNRepositoryImpl.java:292)
at org.tmatesoft.svn.core.io.SVNRepository.getLocations(SVNRepository.java:1088)
at org.tmatesoft.svn.core.io.SVNRepository.getLocations(SVNRepository.java:1516)
at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:178)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:44)
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:20)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:900)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967)
at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872)
at jetbrains.buildServer.buildTriggers.vcs.svn.RepositoryChangesProvider.collectFrom(RepositoryChangesProvider.java:103)
at jetbrains.buildServer.buildTriggers.vcs.svn.RepositoryChangesProvider.loadEntries(RepositoryChangesProvider.java:72)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection$AddChangesProcessor.getEntries(SvnConnection.java:1231)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection$AddChangesProcessor.collect(SvnConnection.java:1005)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection.addChanges(SvnConnection.java:204)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnSupport$SvnIncludeRuleChangeCollector.collectChanges(SvnSupport.java:526)
... 22 more
org.tmatesoft.svn.core.SVNException: svn: E160006: No such revision 11523
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.handleFailureStatus(SVNReader.java:269)
at org.tmatesoft.svn.core.internal.io.svn.SVNReader.parse(SVNReader.java:248)
at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.read(SVNConnection.java:268)
at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.read(SVNRepositoryImpl.java:1290)
at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.getLocationsImpl(SVNRepositoryImpl.java:292)
at org.tmatesoft.svn.core.io.SVNRepository.getLocations(SVNRepository.java:1088)
at org.tmatesoft.svn.core.io.SVNRepository.getLocations(SVNRepository.java:1516)
at org.tmatesoft.svn.core.internal.wc2.SvnRepositoryAccess.getLocations(SvnRepositoryAccess.java:178)
at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgRepositoryAccess.createRepositoryFor(SvnNgRepositoryAccess.java:44)
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:20)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:900)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:967)
at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:872)
at jetbrains.buildServer.buildTriggers.vcs.svn.RepositoryChangesProvider.collectFrom(RepositoryChangesProvider.java:103)
at jetbrains.buildServer.buildTriggers.vcs.svn.RepositoryChangesProvider.loadEntries(RepositoryChangesProvider.java:72)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection$AddChangesProcessor.getEntries(SvnConnection.java:1231)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection$AddChangesProcessor.collect(SvnConnection.java:1005)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection.addChanges(SvnConnection.java:204)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnSupport$SvnIncludeRuleChangeCollector.collectChanges(SvnSupport.java:526)
at jetbrains.buildServer.vcs.CollectRepositoryChangesByIncludeRulesAdapter$1.collectBuildChanges(CollectRepositoryChangesByIncludeRulesAdapter.java)
at jetbrains.buildServer.vcs.VcsSupportUtil.collectBuildChanges(VcsSupportUtil.java:54)
at jetbrains.buildServer.vcs.CollectRepositoryChangesByIncludeRulesAdapter.collectChanges(CollectRepositoryChangesByIncludeRulesAdapter.java:3)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesInSingleRepository.perform(LoadChanges.java:3)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.perform(LoadChanges.java:102)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesForCheckoutRules(LoadChanges.java:90)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChanges(LoadChanges.java:118)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.run(LoadChanges.java:64)
at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader._loadChanges(VcsRootChangesLoader.java:89)
at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader.loadChanges(VcsRootChangesLoader.java:76)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.doLoadChanges(VcsChangesLoaderImpl.java:118)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.loadChangesNoLocking(VcsChangesLoaderImpl.java:115)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.loadChanges(VcsChangesLoaderImpl.java:56)
at jetbrains.buildServer.vcs.impl.VcsManagerImpl.loadChanges(VcsManagerImpl.java:386)
at jetbrains.buildServer.serverSide.impl.auth.SecuredVcsManager.loadChanges(SecuredVcsManager.java:89)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$1.run(VcsModificationChecker.java:25)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
3 comments
Comment actions Permalink

I just downloaded the 7.1 version and the problem is still there:

Error collecting changes for VCS repository 'AgXSpirit Trunk'
org.tmatesoft.svn.core.SVNException: svn: E160006: No such revision 11523

So right now, only svn repositories without external referenses work with TC. A rather serious limitation.

Is there anyone else with this problem?

We have one svn repo with the following structure (one external):


main
  +- external: svn+ssh://svn@svn.x.se/x/trunk

Another with an external repo which in turn has an external ref:

main
  +- external: svn+ssh://svn@svn.x.se/x/trunk
       +- external: svn+ssh://svn@svn.x.se/y/trunk

The only one that works is where I have NO external references at all:

  svn+ssh://svn@svn.x.se/x/trunk


So what can possibly be wrong?
I have verified every individual setting between the 5.0 server and the new 7.0.2 (and 7.1) and I cannot see any difference.
All of the above svn repositories are fully working and accessible from the same computer as on which the server is running. (through tortouise svn).

Helpful for any help.
0
Comment actions Permalink

Hello Anders,

  Did you try setting up a fresh VCS root with externals?

  Are there any errors if you checkout your repository from console, with command-line SVN client?

  Could there be any authentication issues for the externals?

  Related issue in our tracker:   http://youtrack.jetbrains.com/issue/TW-21416


  Regards,
  KIR

0
Comment actions Permalink

The exact same repository (actually there are tens of repositories) all work with TC version 5.0. The settings are copied.
It works as long as the repository does not have external references. The same authorization is used for all repositories (ssh+svn, with a private key and password).

So I can use a svn adress to a repo (on our server) with no external, and it works, then change the repo adress to one with externals (same authorization) and it will not work.

The exact same configuration works fine with TC5.0 (as said before).
It works through command line from linux, mac, windows...

So it all points to recent versions of TC. I have not tested 6.x versions of TC. We are going to upgrade to a enterprise version so we would like this to work first...

/Anders

0

Please sign in to leave a comment.