"failed to collect changes" Mercurial

For what seems like only one part of our whole repository, Team city is unable to access our repo, even while "test connection" is successful. We just upgraded to TC7, and it seems like only this VCS root was affected. Here is the stack trace:

Failed to collect changes, error: 'hg --config ui.interactive=False pull https://nt%5Cteamcity:******@hg.ident.com/OnlinePM/KioskStandalone/Working/' command failed.


jetbrains.buildServer.vcs.VcsException: 'hg --config ui.interactive=False pull https://nt%5Cteamcity:******@hg.ident.com/OnlinePM/KioskStandalone/Working/' command failed.
at jetbrains.buildServer.buildTriggers.vcs.mercurial.command.CommandResult.throwVcsException(CommandResult.java:90)
at jetbrains.buildServer.buildTriggers.vcs.mercurial.command.CommandResult.logAndThrowError(CommandResult.java:80)
at jetbrains.buildServer.buildTriggers.vcs.mercurial.command.CommandResult.checkFailure(CommandResult.java:65)
at jetbrains.buildServer.buildTriggers.vcs.mercurial.command.CommandUtil.runCommand(CommandUtil.java:34)
at jetbrains.buildServer.buildTriggers.vcs.mercurial.command.VcsRootCommand.runCommand(VcsRootCommand.java:32)
at jetbrains.buildServer.buildTriggers.vcs.mercurial.command.PullCommand.call(PullCommand.java:71)
at jetbrains.buildServer.buildTriggers.vcs.mercurial.MercurialVcsSupport.syncRepository(MercurialVcsSupport.java:415)
at jetbrains.buildServer.buildTriggers.vcs.mercurial.MercurialVcsSupport.getBranchesRevisions(MercurialVcsSupport.java:466)
at jetbrains.buildServer.buildTriggers.vcs.mercurial.MercurialVcsSupport.getCurrentState(MercurialVcsSupport.java:453)
at jetbrains.buildServer.vcs.impl.VcsRootInstancesManagerImpl$SVcsRootInstance.getCurrentState(VcsRootInstancesManagerImpl.java:84)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.getCurrentState(VcsChangesLoaderImpl.java:10)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.access$200(VcsChangesLoaderImpl.java:279)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl$6.run(VcsChangesLoaderImpl.java:3)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:117)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.doCollectStates(VcsChangesLoaderImpl.java:229)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.collectStatesForAllRoots(VcsChangesLoaderImpl.java:101)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.getLoadChangesIntervals(VcsChangesLoaderImpl.java:141)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.loadChangesNoLocking(VcsChangesLoaderImpl.java:138)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.tryLoadChanges(VcsChangesLoaderImpl.java:224)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$1$1.run(VcsModificationChecker.java:2)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:117)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$1.run(VcsModificationChecker.java:1)
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)

1 comment
Comment actions Permalink

Update:  I copied the project and and ran it, and it got past that part. Some setting in the project must have been tweaked when we did the upgrade to TC7. I'd be curious to know what that setting is, because it is sure not obvious. Ill keep looking around.

0

Please sign in to leave a comment.