Hi @Panda , That sounds like a great idea; I'm afraid we won't have the resources to add this in the coming weeks (we have some really cool stuff planned for BuildMaster 2022 that we're working on now). The easiest way to do local-development on the extension is to get the source code from GitHub, then build it into dll. Then, construct a new version of the Subversion.upack file with your DLL, and replace the one in the existing extensions folder. From there, restart the web/service, and your version should load instead. If you add properties to SvnRepositoryMonitor.cs that look like the other properties, they should show-up in the UI and be configurable. Let us know what you come up with, and we can definitely merge in the code and release a new version with your changes. Cheers, Alana

We tried to reproduce this, but I get this output, which doesn't include "arguments" and which doesn't put a trailing slash after the destination directory: INFO : 2017-02-22 17:50:04Z - Executing SVN export... DEBUG: 2017-02-22 17:50:04Z - Using TcpAgent agent on GODZILLA DEBUG: 2017-02-22 17:50:04Z - Working directory: DEBUG: 2017-02-22 17:50:04Z - Executing: C:\ProgramData\InedoAgent\BuildMaster\ExtensionsTemp\Subversion\Resources\svn.exe export "https://github.com/Inedo/bmx-subversion/trunk/" "C:\ProgramData\InedoAgent\BuildMaster\Temp\_E78\_D0" --non-interactive --trust-server-cert DEBUG: 2017-02-22 17:50:12Z - A C:\ProgramData\InedoAgent\BuildMaster\Temp\_E78\_D0 [snip] DEBUG: 2017-02-22 17:50:12Z - A C:\ProgramData\InedoAgent\BuildMaster\Temp\_E78\_D0\packages.config DEBUG: 2017-02-22 17:50:12Z - Exported revision 63. INFO : 2017-02-22 17:50:12Z - SVN export executed. Caan you submit the plan and logs in a ticket? Tjhis will be much easier for us to research.

Take a look at the Getting a Simple Application into BuildMaster Tutorial for a good way to get started!

The extension bundles a version of svn.exe, and you can actually find it in and run it from the {BuildMasterInstallDir}\_WEBTMP\ExtTemp\Subversion\Resources\ directory. The command that it runs to validate a connection to a SVN repo is: svn.exe info http://inedo-test-project.googlecode.com/svn/trunk --xml --non-interactive --trust-server-cert [--username xxxx] [--password xxxx] Try that and see what happens when you run it.

Hey Tod, Sorry about the confusion, the error was indeed different. I think we got a bit cross eyed while trying to figure all this out. The setup that we had to use in the end was rather awkward. Buildmaster seems to add quotations around the arguments section. We had the following setup: Command: delete http://<path_to_repo> Argument: -m "ReExecution by Buildmaster" When looking at the logs, it was converting that to: delete http://<path_to_repo> " -m "ReExecution by Buildmaster"" --non-inteactive etc... Notice the double quotations. So we ended up having to jimmy it a bit and it is now working with: Command: delete http://<path_to_repo> -m Argument: ReExecution by Buildmaster So I guess we can scratch this one of the list. Hopefully can present to the boss soon and get some budget for this.

I would suggest just disabling your build schedules during the outage period. Maybe at 12:45AM through 1:15AM (or whatever). This can be done through the API methods (BuildSchedules_GetSchedules and BuildSchedules_CreateOrUpdateSCMTriggered), or through a simple SQL Query (UPDATE BuildSchedules SET Active_Indicator = 'N'). We don't have a generic task scheduler built-in to BuildMaster, so you'd want to use Windows Task scheduler to run the enable/disables.