Not sure I follow your Versioning comment.  Verisoning is handled by our source 
control, not our CI server.  With Continous Integration we are always building 
and testing against the latest code and when we branch, if we want to keep 
running tests and builds on the old branch, we just setup another agent to work 
on that branch.


-----Original Message-----
From: Bob Archer [mailto:[EMAIL PROTECTED]
Sent: Fri 8/15/2008 2:01 PM
To: Steve Kapinos; nant-users@lists.sourceforge.net
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:[EMAIL PROTECTED] 
Sent: Friday, August 15, 2008 1:38 PM
To: Bob Archer; nant-users@lists.sourceforge.net
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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob
Archer
Sent: Friday, August 15, 2008 1:27 PM
To: nant-users@lists.sourceforge.net
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 SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to