I have a general question regarding best practices. I have a small team working on a medium-scale software project, which involves integrating code from different environments, etc. The project is a standalone piece of desktop software.Based on lessons learned from a similar prior project that went badly, I am trying to implement some better software engineering practices.I'd like to start by automating daily builds. We use SVN for source control, and all the developers are working in the trunk, including me. My question is rather simple:Where locally do we do the daily builds? Should I make another folder on my local machine that is the daily build folder? Should I set up a virtual machine? Should I suck it up and do it in my development folder?I understand the revision control paradigms pretty well. I'm mostly looking for how folks implement it in practice.
Daily builds with SVN for a small team
programming practices;svn
A build machine is the way to go, even for small projects/teams. Get any random spare machine (ie. an old dev box). Install some continuous integration software on it like jenkins or teamcity. DoneIt's been a while since I had to set one up or maintain a build machine, but unless it's gotten worse since a year or 2 ago, you can have continuous builds on each checkin, and a nightly build that gets dumped to a network share setup in maybe an hour with either of these products. 