Tag | continuous integration Posts

In a previous blog I describe in twenty one easy steps how to set up continuous integration using a combination of TeamCity and Red Gate tools. Okay, it’s easy only in a relative sense, giving that until recently database continuous integration was almost impossible to set up. One would always suspect that a twenty-one-step process is a long way from the optimal simplicity. Also, having to negotiate the command lines and learning the intricacies of their respective switches and exit codes is tedious ...
I recently switched over to TeamCity from CC.Net. Normally, like most people, I hate change. But, while it took me a while to figure out the new way of configuring a build, it was certainly worth it. Some of the benefits: Being able to copy a configuration to easily start configuration of another. Nifty "pause" feature. Taking responsibility for broken builds Easily viewing build logs in the web interface Client tools (tray, ide integration) I am sure there are others. The list above are benefits ...
I will be presenting a grok talk at Fest07 at Microsoft campus in Reading; 'Continuous Integration for newbies made easy - A quick guide to CI Factory'. Those who have read my posts on CI Factory installation will be familiar with the subject, but feel free to come along and say hello if your attending. I'll have my build server with me - an external notebook drive with VirtualPC image and I'll be giving a brief overview of how CI Factory got my build server up and running in a couple of days, with ...
Here's the culmination of my research into CI Factory and how I'm not using it to develop my open source RapidDB libraries. This is a fairly personal setup, as it only has a single developer (me), two development machines (currently an office desktop PC and a roaming laptop) and a build server which is not publicly accessible via the Internet. An MSDN and Microsoft Partner Action Pack subscription are busy covering my software license requirements. Summary: Development PC 1 : Desktop, XP Pro SP2, ...
I decided to add some unit tests into my first CI Factory project. First I used a reference to MbUnit.Framework.dll in my test project, this is the unit test framework which ships with CI Factory, and all worked fine. No disrespect to MbUnit, but I decided I really wanted to use NUnit so I can utilise the larger amount of documentation and community knowledge that exists for NUnit (even though it might not be as flexible as MbUnit). So I added NUnit 2.2.8 (.NET 2.0 version) underneath my CI Factory ...