By all means. Please picture the following: -A folder full of batch files, each 2,000 lines long, that actually coordinate the builds -A folder full of .exe's

By all means. Please picture the following: -A folder full of batch files, each 2,000 lines long, that actually coordinate the builds -A folder full of .exe's like 'findAndReplace.exe', 'EmailBuildBreakingAuthorsFromSVN.exe', replicating native Jenkins functionality, written in-house -SVN.exe must be installed on the build node; if the build fails, the working copy is usually locked and must be manually Cleaned Up -All build nodes run Windows XP Pro (including the Jenkins master) This is what I had to deal with when I took over the cluster last year!!! For the record, the whole cluster now runs on Win2012 with regular security updates, and most builds use the .Net plugin to build the VS project using msbuild. Those that can't, use Powershell scripts. It has been a VERY long road...