A post involving the use of subversion as my source control system? How could I not use that title? :)
Anyways, whilst I am the only developer working on my own personal projects, source control is still an essential tool. I may not need to sync my work with that done by other developers, but the version tracking that it gives is something that I don't want to be without. Additionally, as I am doing these projects to enhance my knowledge of various tools and best practices, getting a source control system in place is the first step towards being able to build a continuous integration server. The benefits here are far less obvious for a single developer project, but as a learning exercise it is very useful. At the start of a project seems like the best time to get this stuff set up too, so I can focus on getting decent build scripts that run unit tests, code coverage and other analysis all sorted out up-front, so I only have to make minor tweaks to my build as I go along the path of development, rather than try to set it all up further down the road and find things potentially more tricky.
As an aid to setting up my CruiseControl.net server I followed an article on dotnetslackers.com that is part of a series about building an entire website from scratch using all sorts of best practices, just the sort of thing that I want :) (linky). The author mentioned that he was using build 1.5.0.6184 of CC so i decided to use the same build rather than get the latest so I would encounter the same nuances that he did, unfortunately that idea didn't work out as well as I hoped, but I got it running in the end. I wonder how much smoother some of my past projects might have been had I discovered this stuff earlier.
No comments:
Post a Comment