I am getting the following error on my TeamCity project:
Error collecting changes for VCS repository 'MySvnRepository'
Unable to get SVN log entries for: https://myserver/svn/trunk; range:
RR[99_2013/08/27 13:35:20 +0100 => 6_2013/08/27 14:40:13
+0100]@d2fecd1e-4276-d847-874c-cb6b9eafeb43; revisions: 99..6
I have tested the VCS connection through the «Test Connection» button in the TeamCity admin screen and it connects fine.
Looking at the error message it looks as though it is trying to retrieve entries 6 — 99, but there are only 6 log entries in the repository as it is newly created. I have checked that the build counter has been reset.
Is there something obvious I am missing here?
alroc
27.2k6 gold badges50 silver badges95 bronze badges
asked Aug 27, 2013 at 13:51
Declan McNultyDeclan McNulty
3,1246 gold badges34 silver badges53 bronze badges
We had faced similar issue with team city. Seems problem was some how it was trying to fetch the SVN logs from two configurations. Because we had used the same VCS root for 2 different branches at different times.
To solve this, delete and recreate the build configuration as well as the VCS root and it should work.
answered Oct 18, 2013 at 9:41
2
I’m not sure why this worked for me, but I went into the VCS config and changed the SVN Client version from 1.6 to 1.7, and then everything started working.
answered Sep 23, 2014 at 16:08
MikeMike
8077 silver badges20 bronze badges
1
This is old but something that comes up for me from time to time. The problem happens when you repoint an existing project at a different SVN root. If you look at the request TeamCity is making (99_2013/08/27 13:35:20 +0100 => 6_2013/08/27 14:40:13 +0100) you’ll see it’s trying to find the changes from revision 99 to 6 (which obviously there are none). The 99, I suspect, is the last revision before you re-pointed the SVN root of the project to the new one, that has 6 revisions in it. I have the same problem and yes, deleting the VCS root (not just detach) will fix this but that’s not an option for anyone who’s reusing a VCS root among many projects (like me). I don’t know an option here, last time it happened to me I just checked in some bogus changes to get my repo to bump up to 1+ rev over what TeamCity was looking for, however today I’m facing this problem going from 2099 changes to 3. Maybe there’s an SVN thing you can do but other than deleting the VCS root I don’t know what to do on the TeamCity side. I’ve even deleted the project and created a new one, the problem lies in some cache TeamCity has for that repo and what the counters are at.
answered Feb 26, 2015 at 14:49
Bil SimserBil Simser
1,6931 gold badge19 silver badges27 bronze badges
Created a brand new TeamCity build project and configuration along w/ a new VCS root and receive the following errors on the first check for revisions
TeamCity 8.0.6 (build 27767) running on CentOS 6.
Failed to start build #2 on Web Cluster #1
Failed to collect changes, error: Error collecting changes for VCS repository '"rvdealers-trunk" {instance id=9, parent internal id=9, parent id=NationalRvDealers_RvdealersTrunk, description: "svn: svn://svn.masteredge.corp/rvdealers/trunk"}'
Unable to get SVN log entries for: svn://svn.masteredge.corp/rvdealers/trunk; range: RR[9_2014/02/24 23:19:19 -0500 => 11_2014/02/24 23:48:03 -0500]@a3daeacc-e5f5-4bd8-a1b2-caa81242066d; revisions: 9..11
VCS problem: rvdealers-trunk
Error collecting changes for VCS repository '"rvdealers-trunk" {instance id=9, parent internal id=9, parent id=NationalRvDealers_RvdealersTrunk, description: "svn: svn://svn.masteredge.corp/rvdealers/trunk"}'
Unable to get SVN log entries for: svn://svn.masteredge.corp/rvdealers/trunk; range: RR[9_2014/02/24 23:19:19 -0500 => 11_2014/02/24 23:48:03 -0500]@a3daeacc-e5f5-4bd8-a1b2-caa81242066d; revisions: 9..11
I’ve tried deleting and recreating the vcs root, build configuration, and even the project, this occurs as soon as TeamCity tries checking for revisions.
The build agent trying to run the build resides on a different server, running Windows 2008. This project is .NET so the TeamCity host is unable to run the build.
TeamCity and the SVN server are both running on the same server.
I can post the stack-trace if anybody thinks it might be helpful, just didn’t because it’s super long. I’ve got 4 other projects setup successfully, exactly the same as this, but this is the only one that doesn’t work.
I am getting the following error on my TeamCity project:
Error collecting changes for VCS repository 'MySvnRepository'
Unable to get SVN log entries for: https://myserver/svn/trunk; range:
RR[99_2013/08/27 13:35:20 +0100 => 6_2013/08/27 14:40:13
+0100]@d2fecd1e-4276-d847-874c-cb6b9eafeb43; revisions: 99..6
I have tested the VCS connection through the «Test Connection» button in the TeamCity admin screen and it connects fine.
Looking at the error message it looks as though it is trying to retrieve entries 6 — 99, but there are only 6 log entries in the repository as it is newly created. I have checked that the build counter has been reset.
Is there something obvious I am missing here?
We had faced similar issue with team city. Seems problem was some how it was trying to fetch the SVN logs from two configurations. Because we had used the same VCS root for 2 different branches at different times.
To solve this, delete and recreate the build configuration as well as the VCS root and it should work.
I am getting the following error on my TeamCity project:
Error collecting changes for VCS repository 'MySvnRepository' Unable to get SVN log entries for: https://myserver/svn/trunk; range: RR[99_2013/08/27 13:35:20 +0100 => 6_2013/08/27 14:40:13 +0100]@d2fecd1e-4276-d847-874c-cb6b9eafeb43; revisions: 99..6I have tested the VCS connection through the “Test Connection” button in the TeamCity admin screen and it connects fine.
Looking at the error message it looks as though it is trying to retrieve entries 6 – 99, but there are only 6 log entries in the repository as it is newly created. I have checked that the build counter has been reset.
Is there something obvious I am missing here?
Answer
We had faced similar issue with team city. Seems problem was some how it was trying to fetch the SVN logs from two configurations. Because we had used the same VCS root for 2 different branches at different times.
To solve this, delete and recreate the build configuration as well as the VCS root and it should work.
Attribution
Source : Link , Question Author : Declan McNulty , Answer Author : Narain Mittal
Это старо, но что-то, что приходит ко мне время от времени. Проблема возникает, когда вы перенаправляете существующий проект в другой корень SVN. Если вы посмотрите на запрос TeamCity (99_2013/08/27 13:35:20 +0100 => 6_2013/08/27 14:40:13 +0100), вы увидите, что он пытается найти изменения из версии 99. до 6 (которых, очевидно, нет). Я подозреваю, что 99 — это последняя ревизия перед тем, как вы переназначили корень проекта SVN на новую, в которой есть 6 ревизий. У меня та же проблема, и да, удаление корня VCS (а не просто отсоединение) исправит это, но это не вариант для тех, кто повторно использует корень VCS во многих проектах (например, я). Я не знаю варианта здесь, в прошлый раз, когда это случилось со мной, я только что проверил некоторые фиктивные изменения, чтобы мое репо увеличилось до 1+ оборотов по сравнению с тем, что искал TeamCity, однако сегодня я столкнулся с этой проблемой, начиная с 2099 меняется на 3. Может быть, вы можете сделать что-то с SVN, но кроме удаления корня VCS я не знаю, что делать на стороне TeamCity. Я даже удалил проект и создал новый, проблема заключается в каком-то кеше, который TeamCity имеет для этого репо, и в том, на чем находятся счетчики.
Создан 26 фев.
Hi,
after upgrading to newest teamcity plastic plugin I noticed that plugin does not work. I get following error when trying to build project:
Before update the plugin was working correctly.
Error collecting changes for VCS repository '...'
Error getting diff info of 1039: Error: Input string was not in a correct format.
Hide stacktrace
jetbrains.buildServer.vcs.VcsRootVcsException: Error collecting changes for VCS repository '..." {instance id=193, parent internal id=19, parent id=XConnect_XConnectPlasticSCM1, description: "PlasticSCM: ..."}'
Error getting diff info of 1039: Error: Input string was not in a correct format.
at jetbrains.buildServer.buildTriggers.vcs.ConnectionStateReporterImpl.reportConnectionFailed(ConnectionStateReporterImpl.java:28)
at jetbrains.buildServer.buildTriggers.vcs.ConnectionStateReporterImpl.reportConnectionFailed(ConnectionStateReporterImpl.java:5)
at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader$RunLoadChanges.run(VcsRootChangesLoader.java:29)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:74)
at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader.loadChanges(VcsRootChangesLoader.java:119)
at jetbrains.buildServer.vcs.impl.VcsChangesFetcher$LoadChangesForRoot.run(VcsChangesFetcher.java:2)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl$ImmediateFutureExecService$1.call(VcsChangesLoaderImpl.java:3)
at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:59)
at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:68)
at jetbrains.buildServer.vcs.impl.VcsChangesSyncFetcher.waitForTasksToComplete(VcsChangesSyncFetcher.java:16)
at jetbrains.buildServer.vcs.impl.VcsChangesSyncFetcher.doLoadChanges(VcsChangesSyncFetcher.java:12)
at jetbrains.buildServer.vcs.impl.VcsChangesSyncFetcher.tryLoadChanges(VcsChangesSyncFetcher.java:17)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.tryLoadChanges(VcsChangesLoaderImpl.java:1)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction$1.run(VcsModificationChecker.java:12)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:74)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction.run(VcsModificationChecker.java:1)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: jetbrains.buildServer.vcs.VcsException: Error getting diff info of 1039: Error: Input string was not in a correct format.
at com.codicesoftware.plugins.teamcity.PlasticCollectChangesPolicy.buildModificationData(PlasticCollectChangesPolicy.java:172)
at com.codicesoftware.plugins.teamcity.PlasticCollectChangesPolicy.getDifferencesBetweenVersions(PlasticCollectChangesPolicy.java:104)
at com.codicesoftware.plugins.teamcity.PlasticCollectChangesPolicy.collectChanges(PlasticCollectChangesPolicy.java:61)
at jetbrains.vcs.api.services.collectChanges.CollectRepositoryChangesPolicyFactory$3.collectChanges(CollectRepositoryChangesPolicyFactory.java:2)
at jetbrains.vcs.api.services.collectChanges.CollectChangesServiceProvider$1.collectChanges(CollectChangesServiceProvider.java:7)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesForCheckoutRules.call(LoadChanges.java:13)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesForCheckoutRules.call(LoadChanges.java:4)
at jetbrains.buildServer.vcs.VcsOperationProgressProviderImpl.runWithProgress(VcsOperationProgressProviderImpl.java:27)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesWithProgress(LoadChanges.java:59)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesForCheckoutRules(LoadChanges.java:6)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesByCombinedRule(LoadChanges.java:36)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChanges(LoadChanges.java:7)
at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader$RunLoadChanges.run(VcsRootChangesLoader.java:6)
... 18 more
Caused by: com.codicesoftware.plastic.core.PlasticException: Error: Input string was not in a correct format.
at com.codicesoftware.plastic.core.PlasticShell.execute(Unknown Source)
at com.codicesoftware.plastic.commands.DiffCommand.execute(Unknown Source)
at com.codicesoftware.plugins.teamcity.PlasticCollectChangesPolicy.buildModificationData(PlasticCollectChangesPolicy.java:165)
... 30 more
jetbrains.buildServer.vcs.VcsException: Error getting diff info of 1039: Error: Input string was not in a correct format.
at com.codicesoftware.plugins.teamcity.PlasticCollectChangesPolicy.buildModificationData(PlasticCollectChangesPolicy.java:172)
at com.codicesoftware.plugins.teamcity.PlasticCollectChangesPolicy.getDifferencesBetweenVersions(PlasticCollectChangesPolicy.java:104)
at com.codicesoftware.plugins.teamcity.PlasticCollectChangesPolicy.collectChanges(PlasticCollectChangesPolicy.java:61)
at jetbrains.vcs.api.services.collectChanges.CollectRepositoryChangesPolicyFactory$3.collectChanges(CollectRepositoryChangesPolicyFactory.java:2)
at jetbrains.vcs.api.services.collectChanges.CollectChangesServiceProvider$1.collectChanges(CollectChangesServiceProvider.java:7)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesForCheckoutRules.call(LoadChanges.java:13)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesForCheckoutRules.call(LoadChanges.java:4)
at jetbrains.buildServer.vcs.VcsOperationProgressProviderImpl.runWithProgress(VcsOperationProgressProviderImpl.java:27)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesWithProgress(LoadChanges.java:59)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesForCheckoutRules(LoadChanges.java:6)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesByCombinedRule(LoadChanges.java:36)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChanges(LoadChanges.java:7)
at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader$RunLoadChanges.run(VcsRootChangesLoader.java:6)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:74)
at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader.loadChanges(VcsRootChangesLoader.java:119)
at jetbrains.buildServer.vcs.impl.VcsChangesFetcher$LoadChangesForRoot.run(VcsChangesFetcher.java:2)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl$ImmediateFutureExecService$1.call(VcsChangesLoaderImpl.java:3)
at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:59)
at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:68)
at jetbrains.buildServer.vcs.impl.VcsChangesSyncFetcher.waitForTasksToComplete(VcsChangesSyncFetcher.java:16)
at jetbrains.buildServer.vcs.impl.VcsChangesSyncFetcher.doLoadChanges(VcsChangesSyncFetcher.java:12)
at jetbrains.buildServer.vcs.impl.VcsChangesSyncFetcher.tryLoadChanges(VcsChangesSyncFetcher.java:17)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.tryLoadChanges(VcsChangesLoaderImpl.java:1)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction$1.run(VcsModificationChecker.java:12)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:74)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction.run(VcsModificationChecker.java:1)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.codicesoftware.plastic.core.PlasticException: Error: Input string was not in a correct format.
at com.codicesoftware.plastic.core.PlasticShell.execute(Unknown Source)
at com.codicesoftware.plastic.commands.DiffCommand.execute(Unknown Source)
at com.codicesoftware.plugins.teamcity.PlasticCollectChangesPolicy.buildModificationData(PlasticCollectChangesPolicy.java:165)
... 30 more
com.codicesoftware.plastic.core.PlasticException: Error: Input string was not in a correct format.
at com.codicesoftware.plastic.core.PlasticShell.execute(Unknown Source)
at com.codicesoftware.plastic.commands.DiffCommand.execute(Unknown Source)
at com.codicesoftware.plugins.teamcity.PlasticCollectChangesPolicy.buildModificationData(PlasticCollectChangesPolicy.java:165)
at com.codicesoftware.plugins.teamcity.PlasticCollectChangesPolicy.getDifferencesBetweenVersions(PlasticCollectChangesPolicy.java:104)
at com.codicesoftware.plugins.teamcity.PlasticCollectChangesPolicy.collectChanges(PlasticCollectChangesPolicy.java:61)
at jetbrains.vcs.api.services.collectChanges.CollectRepositoryChangesPolicyFactory$3.collectChanges(CollectRepositoryChangesPolicyFactory.java:2)
at jetbrains.vcs.api.services.collectChanges.CollectChangesServiceProvider$1.collectChanges(CollectChangesServiceProvider.java:7)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesForCheckoutRules.call(LoadChanges.java:13)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges$CollectChangesForCheckoutRules.call(LoadChanges.java:4)
at jetbrains.buildServer.vcs.VcsOperationProgressProviderImpl.runWithProgress(VcsOperationProgressProviderImpl.java:27)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesWithProgress(LoadChanges.java:59)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesForCheckoutRules(LoadChanges.java:6)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChangesByCombinedRule(LoadChanges.java:36)
at jetbrains.buildServer.buildTriggers.vcs.LoadChanges.collectChanges(LoadChanges.java:7)
at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader$RunLoadChanges.run(VcsRootChangesLoader.java:6)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:74)
at jetbrains.buildServer.buildTriggers.vcs.VcsRootChangesLoader.loadChanges(VcsRootChangesLoader.java:119)
at jetbrains.buildServer.vcs.impl.VcsChangesFetcher$LoadChangesForRoot.run(VcsChangesFetcher.java:2)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl$ImmediateFutureExecService$1.call(VcsChangesLoaderImpl.java:3)
at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:59)
at jetbrains.buildServer.serverSide.impl.ImmediateFuture.get(ImmediateFuture.java:68)
at jetbrains.buildServer.vcs.impl.VcsChangesSyncFetcher.waitForTasksToComplete(VcsChangesSyncFetcher.java:16)
at jetbrains.buildServer.vcs.impl.VcsChangesSyncFetcher.doLoadChanges(VcsChangesSyncFetcher.java:12)
at jetbrains.buildServer.vcs.impl.VcsChangesSyncFetcher.tryLoadChanges(VcsChangesSyncFetcher.java:17)
at jetbrains.buildServer.vcs.impl.VcsChangesLoaderImpl.tryLoadChanges(VcsChangesLoaderImpl.java:1)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction$1.run(VcsModificationChecker.java:12)
at jetbrains.buildServer.util.NamedThreadFactory.executeWithNewThreadName(NamedThreadFactory.java:74)
at jetbrains.buildServer.serverSide.impl.VcsModificationChecker$CollectChangesAction.run(VcsModificationChecker.java:1)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
В моем проекте TeamCity появляется следующая ошибка:
Error collecting changes for VCS repository 'MySvnRepository'
Unable to get SVN log entries for: https://myserver/svn/trunk; range:
RR[99_2013/08/27 13:35:20 +0100 => 6_2013/08/27 14:40:13
+0100]@d2fecd1e-4276-d847-874c-cb6b9eafeb43; revisions: 99..6
Я проверил соединение VCS с помощью кнопки «Проверить соединение» на экране администратора TeamCity, и оно подключается нормально.
Глядя на сообщение об ошибке, кажется, что оно пытается получить записи с 6 по 99, но в репозитории всего 6 записей журнала, поскольку он создается заново. Я проверил, что счетчик сборки сброшен.
Есть ли что-то очевидное, чего мне здесь не хватает?
4 ответа
Лучший ответ
Мы столкнулись с аналогичной проблемой с командным городом. Кажется, проблема заключалась в том, как он пытался получить журналы SVN из двух конфигураций. Потому что мы использовали один и тот же корень VCS для двух разных веток в разное время.
Чтобы решить эту проблему, удалите и воссоздайте конфигурацию сборки, а также корень VCS, и она должна работать.
7
Narain Mittal
18 Окт 2013 в 13:41
Я не уверен, почему это сработало для меня, но я вошел в конфигурацию VCS и изменил версию SVN Client с 1.6 на 1.7, а затем все начало работать.
2
Mike
23 Сен 2014 в 20:08
Это старое, но кое-что мне приходит время от времени. Проблема возникает, когда вы перенаправляете существующий проект в другой корень SVN. Если вы посмотрите на запрос, который делает TeamCity (99_2013 / 08/27 13:35:20 +0100 => 6_2013 / 08/27 14:40:13 +0100), вы увидите, что он пытается найти изменения из ревизии 99. до 6 (которых, очевидно, нет). Я подозреваю, что 99 — это последняя ревизия перед тем, как вы перенаправили корень SVN проекта на новую, в которой есть 6 ревизий. У меня та же проблема, и да, удаление корня VCS (а не просто отсоединение) исправит это, но это не вариант для тех, кто повторно использует корень VCS во многих проектах (например, я). Я не знаю здесь варианта, в прошлый раз, когда это случилось со мной, я только что проверил некоторые фиктивные изменения, чтобы мое репо увеличилось до 1+ оборотов по сравнению с тем, что искал TeamCity, однако сегодня я столкнулся с этой проблемой, идущей от 2099 меняется на 3. Возможно, вы можете сделать что-то с SVN, но кроме удаления корня VCS, я не знаю, что делать на стороне TeamCity. Я даже удалил проект и создал новый, проблема заключается в каком-то кеше, который есть у TeamCity для этого репо, и в том, где находятся счетчики.
0
Bil Simser
26 Фев 2015 в 17:49