From: Bevan A. <Bev...@rb...> - 2008-08-17 23:17:31
|
Hi Bob. We've recently adopted TeamCity, and I've found the whole point/click interface to be a real bonus because *other people* will be able to look after the builds, not just me. CruiseControl.NET is capable and reliable, but the knowledge barrier to entry is pretty high - and I didn't want to be the only one able to maintain the builds. I'm not sure what you want from your CI server wrt versioning - if you just want to apply a label to the code in a particular build, TeamCity supports that out of the box. Otherwise, yes, you need to write a script using NAnt or your tool of choice. Even though we're using TeamCity Professional (ie: the free edition), we've found the support from JetBrains to be first-class: the couple of questions we've posed have been answered both quickly and accurately. Just my 2c, Bevan. From: nan...@li... [mailto:nan...@li...] On Behalf Of Bob Archer Sent: Saturday, 16 August 2008 6:02 a.m. To: Steve Kapinos; nan...@li... Subject: Re: [NAnt-users] cc.net and nant and msbuild Steven, Thanks much. I looked at Team City over the past few days and just didn't see any advantage to it. Yes, it has some nice features. But, the way it touts that you can set up your build with point/click interface is well not so true. If all you do is compile and run unit tests. But, what about versioning as a simple example. Well, I would have to create a Nant script (or build plug-in). Same with any thing else I would have to do. The biggest advantage for us would have been the build agents. We build some VB6 code so each version has to run independently due to DLL registration. I also looked at Final builder, which does do a lot of stuff out of the box using an IDE, but it is pretty expensive. My budget for this is $0 so open source license price is right. I wonder if your previous issues were with CC.Net or actually with sourcesafe and bat files. Thanks for your input. BOb ________________________________ From: Steve Kapinos [mailto:Ste...@ta...] Sent: Friday, August 15, 2008 1:38 PM To: Bob Archer; nan...@li... Subject: RE: [NAnt-users] cc.net and nant and msbuild We moved from CC.net to teamcity with very good success. CC.net was problematic for us at times. Moved from CC.net, sourcesafe, and bat files to team-city, nant, and svn in one fell swoop. In our setups, source control is handled by teamcity mostly, but some scripts have source checkout in them (using exec not the svn components of nant). We build from a clean directory each time rather then rebuild. Teamcity has been very good to us as a CI platform and integrates very cleanly with nant and svn -Steve From: nan...@li... [mailto:nan...@li...] On Behalf Of Bob Archer Sent: Friday, August 15, 2008 1:27 PM To: nan...@li... Subject: [NAnt-users] cc.net and nant and msbuild Hi All, I am curious... when you have CC.Net setup up with a subversion source control block, does it do an update of the workingDirectory? Or, do you need to do that in your nant build file? I'm confused if the autoGetSource means it does updates or just checkouts when there is no _svn folder. Also, if you tell MSBuild to do a Rebuild... does that mean it deletes all of the obj/bin folders first by itself... or are you guys doing this in your nant scripts? Yes, I am re-working my builds again... decided to move away from CI Factory, although I did get a lot of great ideas from its scripts. BOb ****************************************************************************** "This message (and any files transmitted with it) are confidential and may be legally privileged. If you are not the intended recipient please notify the sender immediately and delete this message from your system. This message does not necessarily reflect the views of the Reserve Bank of New Zealand. If the recipient has any concerns about the content of this message they should seek alternative confirmation from the Reserve Bank of New Zealand." ****************************************************************************** |