Problems with VCS connection
After switching over to a new source code repository (subversion), I started getting the "Problems with VCS connection" error. I'm not sure what the problem is. When I go to edit the VCS root, I notice the message "This VCS root is used in more than one build configuration. Please choose corresponding option for applying changes in this VCS root." After I set that to "Apply to all configurations of AIS project" everything seems to be working for about 30 seconds, but then the error comes back and I get the same warning message about the VCS root as if I had never set the option. Here's the details of the "Problems" error:
java.lang.NullPointerException
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection.createStringRevision(SvnConnection.java:244)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnConnection.addChanges(SvnConnection.java:227)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnSupport.collectBuildChanges(SvnSupport.java:287)
at jetbrains.buildServer.vcs.VcsSupportUtil.collectBuildChanges(VcsSupportUtil.java:37)
at jetbrains.buildServer.buildTriggers.vcs.svn.SvnSupport.collectBuildChanges(SvnSupport.java:199)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.collectBuildChanges(VcsChangesLoader.java:37)
at jetbrains.buildServer.buildTriggers.vcs.VcsChangesLoader.loadChanges(VcsChangesLoader.java:164)
at jetbrains.buildServer.vcs.impl.VcsManagerImpl.loadChanges(VcsManagerImpl.java:169)
at jetbrains.buildServer.serverSide.impl.auth.SecuredVcsManager.loadChanges(SecuredVcsManager.java:61)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$1.run(VcsModificationChecker.java:11)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:417)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:269)
at java.util.concurrent.FutureTask.run(FutureTask.java:123)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
And ideas?
-Aaron
Please sign in to leave a comment.
Hello Aaron,
What version of TeamCity do you use? This bug should have been fixed in TeamCity 4.0.2.
Regards,
KIR
Ahah! It appears I am using the newly-antiquated 4.0.1. I shall upgrade. Thanks!
-Aaron
That seems to have fixed the problem.
Thanks
-Aaron