We are experiencing an issue with our SVN repos currently. Recently upgraded to v1.5.0.295.
The following error is being thrown and all the projects that use this repo are throwing a build error or pausing as the repo has been in a constant error state.
I have tried resetting the repo in the UI, but this has not helped.
I have included the full error output below.
Repository
Cannot get changes for repository StaffPlan-SVN: Exception: ArgumentOutOfRangeException
Message: startIndex cannot be larger than length of string.
Parameter name: startIndex
Stack Trace: at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
at Continua.Modules.Builds.Repositories.Subversion.GetNewChangesetsForRepositoryFolder(String workingFolder, Int32& highestRev, Boolean isDefaultBranch, Boolean isTag, String repoFolder)
at Continua.Modules.Builds.Repositories.SubversionRepositoryPlugIn.GetNewChangesets(IRepositoryExecutionContext context, IRepositoryCache cache)
at Continua.Modules.Builds.Repositories.Repository.GetNewChangesets(RepositoryCache cache, IRepositoryExecutionContext context)
at Continua.Modules.Builds.Repositories.Repository.GetRepositoryChanges(RepositoryCache cache, IRepositoryExecutionContext context)
This event has been reported 685 times.
Have avoided the error by deleting the repository and using another that points to the same SVN URL (we had a few with different exclude patterns). However now I am seeing some odd behaviour with the ChangeSets. The changes found seems to be almost random, with some finding ‘latest’ changes as commits from weeks ago and projects building old code.
Am used to sometimes very old commits being listed in the changesets seemingly randomly, but never that the code that is compiled is not the latest.
Hi Jason
Can you enable debug logging (see here - http://wiki.finalbuilder.com/display/continua/Debug+Logging ) and then reset the repository and once you see the odd behavior send a the debug log to support@finalbuilder.com - that will help us narrow down the cause.
It was some spurious lock… have run a clean-up on all the repos and now it seems to work ok. Thanks for the logging tip, helped a lot .
Hi Jason, that’s great to hear that everything is up and running again for you Thanks again.
Sure thing Peter.
Thanks very much Jason, we appreciate it.