You could potentially add a new field called "subdirectory to monitor", and have its default value be "branches". That way existing users could migrate to the new version, while getting the previous behavior, and new users can change this to get the new behavior.

You would also need to change other places that mention "monitored branches" and similar terminology, to "monitored subdirectories" though.

Even better, you can add another field called "monitor subdirectories" with a default value of true. In my case, I don't really want to monitor subdirectories, just one directory.

I'll probably play around with the plugin code to see what I can do.

Thanks

@atripp Thank you very much for your reply. It is a refreshingly quick, honest and straightforward answer that you rarely see from developers nowadays.

I see. My suspicions were spot on. If the tool expects for there be a "branches" directory, It is quite understandable it breaks when it finds a different structure.

In my opinion, you could just remove the code that adds "branches" to the command. In SVN, "branches" is just a directory that, by convention, a lot of people use to store their branches in, but it is a directory that has nothing special by itself. I can reasonably assume that by removing that, the plugin will work, and instead of monitoring "branches", it can monitor "directories", which is a more generalized solution.

That said, this would be a breaking change, as people who depend on this behavior, would now have to change their settings, and start monitoring the "branches" directory, instead of the directory above.

I didn't know the source code for these plugins was available. I'll probably just make a variant for my own needs. If you have information on how to build my own plugins, that would be great, but I can also look for it myself.

Thanks

I have my source code in a very simple SVN repository that only has my project in it. There's no trunk, branches or tags, just the code tree. This works fine for my needs, and I'm not interested in discussing whether or not this is a good way to organize my SVN repository.

I want to use the SVN repository monitor to detect when the latest revision of a specific folder in my repository has changed, and trigger a build. However, after setting up my repository monitor, I keep on getting the following error:

System.InvalidOperationException: svn: warning: W160013: '/svn/project/!svn/rvr/231/branches' path not found
svn: E200009: Could not list all targets because some targets don't exist
at Inedo.Extensions.Subversion.SvnClient.<EnumerateBranchesAsync>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.Extensions.Subversion.RepositoryMonitors.SvnRepositoryMonitor.<GetCurrentCommitsAsync>d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Inedo.BuildMaster.Windows.ServiceApplication.RepositoryMonitorRunner.<CheckRepositoryAsync>d__3.MoveNext()

It seems like the repository monitor is expecting for my repository to have a specific structure (have a "branches" directory), and since the repository is not organized in that way, it throws an error.

Is there a way to have a repository monitor simply monitor a directory? no branches or anything else?

Thanks