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 anot
I'm not too familiar with the VB6 stuff. But, we use a tool that builds
the VB6 stuff. It updates dependencies and version numbers and such.
Then, and DLLs or .vbps that are updated get committed back to the
repository. I just use the Nant task to run the g7x builder.
The tool is http://www.g7x.co
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
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 th
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.
