DevPinoy.org
A Filipino Developers Community
   
Continuous Integration rocks; AnkhSVN sucks
I'm midway into my second week at my new employer, and I must say that continuous integration is great. Everyone is quickly in sync and there's immediate feedback that you don't get when you're not using CI. I must admit that since it's my first time to work with CruiseControl.NET, I was intimidated at first and very hesitant to do my first "check-in dance." True enough, my first check-in resulted in a red CCTray icon on the system tray, meaning the build is broken. Stick out tongue I was able to gather enough wits to find the location of the problem, do another check-in dance then see a green icon a few minutes later. Smile

Meanwhile, AnkhSVN sucks. Well the idea is nice but the implementation isn't stellar. I did a commit using it (since it's integrated into Visual Studio) but it only committed the source files, not the .csproj file. As a result, yep, a broken build because of some missing class which was there anyway! Oh well, I'll just do TortoiseSVN accesses when working with our Subversion repository. By the way, it's great to finally be free from the shackles of Visual SourceSafe and its terrible exclusive check out way of doing things.

Now back to learning about .NET remoting and Windows Forms... Smile

Posted 01-10-2007 4:56 PM by cruizer
Filed under: , , ,

Comments

rdagumampan wrote re: Continuous Integration rocks; AnkhSVN sucks
on 01-10-2007 8:34 AM

I  dont know what happened to AnkhSVN but now Im using VisualSVN. Its simple and easy to use and still uses the TortoiseSVN windows, it just lock your IDE and you dont have to goto winexplorer.

cruizer wrote re: Continuous Integration rocks; AnkhSVN sucks
on 01-10-2007 12:52 PM

thanks for the heads up, dehran :) looks good and works with TortoiseSVN...

undetected wrote re: Continuous Integration rocks; AnkhSVN sucks
on 01-16-2007 7:55 AM

In our case, I set up CruiseCtrl because another team kept causing compile errors.  Our code had another team's code as dependency, and they weren't looking to see if their code broke our build.  Now, with CC, both teams get an email when someone checks in something that breaks the build, no matter who.

on 04-02-2009 8:47 AM

Bookmarked your page with keywords ankhsvn!

Copyright DevPinoy 2005-2008