[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Help migrating workflow from p4 to svn.

From: Adam Messinger <adam_messinger_at_mac.com>
Date: 2005-05-27 20:26:42 CEST

I'm experimenting with using svn instead of p4. However I'm having
difficulty figuring out how to migrate one bit of our workflow to svn.

Currently we set a p4 label (which is just a symbolic alias to a
revision number) from Cruise Control each time a clean build occurs
in the trunk. This label moves several times an hour and typically
trails the head change by a handful of changes. Developers who don't
want to risk grabbing changes that break the build in their working
copy update at the label rather than at the head. Developers then
make their changes, test, and checkin the change (sometimes an
additional update and resolve is required if the same files have
changed in the working copy and in the repository between the label
and head).

Is there a way to accomplish a similar workflow using svn? I've
looked back through the mailing list archives and it seems that
whenever the topic of p4 labels comes up people suggest using svn
tags. I've looked at this, but I can't see how to make it work here
because one would need to checkout from a tag, but then checkin to
the trunk. I apologize if I'm missing something obvious here.



To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri May 27 20:42:14 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.