> -----Original Message-----
> From: Blair Zajac [mailto:blair@orcaware.com]
> On Oct 25, 2007, at 4:20 PM, SI COM wrote:
>
> > All:
> >
> > I know a lot of folks have asked this before, but I am
> going to do it
> > again.
> >
> > I am part of the SCM team that is evaluating a replacement
> for VSS and
> > Subversion is one of the choices at this point. So here are the
> > questions that I have:
> >
>
> > 2) We have invested a lot in creating push button builds ( any user
> > can create a build from a web page) so how good are the APIs that
> > Subversion provides?
>
> The API is very good. Using the Python bindings, for
> example, you can tie into any part of the Subversion
> infrastructure, from directly opening the Subversion
> repository, to remote client commands. The API is also the
> reason why there are so many Subversion GUI clients, they all
> make use of the C Subversion API.
If you use (N)Ant, there are SVN tasks in the contrib project. We are
also on the brink of choosing a replacement for VSS, and Subversion is
one of the top two.
Some things to note:
1) Subversion lacks the whiz-bang polished features that many commercial
products offer. As a tech, you will find that many of them are cute,
but not necessary. Your management might feel differently.
2) Security management appears to be a bit rough around the edges to me
(I'm exploring it now, see my earlier post). Where commercial products
will give a very fine grained security model, the SVN way is much more
basic. You can get the more complex capabilities with commit event
hooks.
3) The simple "svnserve" server is very effective and easy to use. If
you want more polish (at the cost of increased setup requirements) look
at the Apache setup. There are some more administrative tools available
for this setup. I'm going to review http://svnmanager.sourceforge.net/
for security administration, for example. We're planning to use
svnserve here, though, which means I might have to write my own GUI for
security maintenance.
4) If you're in a VS 2003 environment, the "switch" feature is a Godsend
for ASP.NET projects and branching. http://ankhsvn.tigris.org/ is an
exellent integration plugin for VS 2003 and VS 2005.
5) http://www.statsvn.org/ will make your project manager and tech lead
very happy.
6) Research the svndumpfilter tool filters vis-a-vis file copy. Then
check out svndumpfilter3 at http://furius.ca/pubcode/#subversion-tools
7) Merge tracking is a critical feature. It will be part of Subversion
1.5. In the meantime, take a look at svnmerge.py, located at
http://svn.collab.net/repos/svn/trunk/contrib/client-side/ with lots of
other useful scripts.
8) If you want to get fancy with your "continuous integration", and need
a high level of control of what gets committed where, take a look at
http://sin.tigris.org/ (personally, this level of complexity is
unappealing to me)
9) More useful utilities can be found at
http://www.subversionary.org/taxonomy_menu/1/12/7
You probably can tell that I'm well along in this review process ;)
--
David
*************************************************************************
This communication, including attachments, is
for the exclusive use of addressee and may contain proprietary,
confidential and/or privileged information. If you are not the intended
recipient, any use, copying, disclosure, dissemination or distribution is
strictly prohibited. If you are not the intended recipient, please notify
the sender immediately by return e-mail, delete this communication and
destroy all copies.
*************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 26 14:16:56 2007