Comments on: Set the revision of your svn:externals (or else!) http://thinkinging.com/2008/10/21/set-the-revision-of-your-svnexternals-or-else/ an unfiltered stream of data flow consciousness Wed, 11 Aug 2010 09:38:19 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Abhimanyu Grover http://thinkinging.com/2008/10/21/set-the-revision-of-your-svnexternals-or-else/comment-page-1/#comment-25454 Abhimanyu Grover Mon, 19 Jul 2010 06:37:49 +0000 http://thinkinging.com/?p=633#comment-25454 We're facing exact problem, we have like 10-14 external repositories linked per project and its a pain in a** to tag each and every repo manually. I am starting to write a Phing (ANT of PHP) task to do this automatically if anyone has not done this before? We’re facing exact problem, we have like 10-14 external repositories linked per project and its a pain in a** to tag each and every repo manually.

I am starting to write a Phing (ANT of PHP) task to do this automatically if anyone has not done this before?

]]> By: Vlad http://thinkinging.com/2008/10/21/set-the-revision-of-your-svnexternals-or-else/comment-page-1/#comment-25452 Vlad Mon, 01 Mar 2010 12:19:29 +0000 http://thinkinging.com/?p=633#comment-25452 >Make sure that your trunk specifies the revision of svn:externals >before you create a tag. You >can always unset the >svn:externals revision in the trunk, after you create the tag. I can propose the following solution: 1. Check out branch or trunk which should be tagged. 2. Freeze revisions of all externals in the working copy by editing svn:externals property on the working copy. 3. Use `svn copy` to copy the working copy to a new tag location in the repository. This way the tag will contain the exact copy of the code with freezed externals revisions. On the other hand, you don't have to set and unset properties in the repository, which may be highly undesirable epsecially if we consider trunk with many developers working on it. >Make sure that your trunk specifies the revision of svn:externals
>before you create a tag. You >can always unset the
>svn:externals revision in the trunk, after you create the tag.

I can propose the following solution:

1. Check out branch or trunk which should be tagged.
2. Freeze revisions of all externals in the working copy by editing svn:externals property on the working copy.
3. Use `svn copy` to copy the working copy to a new tag location in the repository.

This way the tag will contain the exact copy of the code with freezed externals revisions.
On the other hand, you don’t have to set and unset properties in the repository, which may be highly undesirable epsecially if we consider trunk with many developers working on it.

]]> By: Jim Kring http://thinkinging.com/2008/10/21/set-the-revision-of-your-svnexternals-or-else/comment-page-1/#comment-25450 Jim Kring Wed, 24 Feb 2010 18:48:24 +0000 http://thinkinging.com/?p=633#comment-25450 Pedro, I have no idea if this is "fixed", yet. Pedro, I have no idea if this is “fixed”, yet.

]]> By: Pedro Pereira http://thinkinging.com/2008/10/21/set-the-revision-of-your-svnexternals-or-else/comment-page-1/#comment-25449 Pedro Pereira Wed, 24 Feb 2010 15:27:12 +0000 http://thinkinging.com/?p=633#comment-25449 is this "fixed" already? is there any new features on subversion that tags the externals? is this “fixed” already? is there any new features on subversion that tags the externals?

]]> By: Jim Kring http://thinkinging.com/2008/10/21/set-the-revision-of-your-svnexternals-or-else/comment-page-1/#comment-25448 Jim Kring Fri, 15 Jan 2010 03:40:58 +0000 http://thinkinging.com/?p=633#comment-25448 Hi Rick, that bug sounds like a real pain, especially since users can't really tell whether they are looking at a folder in Windows that is an SVN external of the parent folder. Do you put some file in that parent folder that says something like "DO NOT SVN UPDATE CHILD FOLDERS"? Hi Rick, that bug sounds like a real pain, especially since users can’t really tell whether they are looking at a folder in Windows that is an SVN external of the parent folder. Do you put some file in that parent folder that says something like “DO NOT SVN UPDATE CHILD FOLDERS”?

]]> By: Rick B http://thinkinging.com/2008/10/21/set-the-revision-of-your-svnexternals-or-else/comment-page-1/#comment-25447 Rick B Fri, 15 Jan 2010 02:39:20 +0000 http://thinkinging.com/?p=633#comment-25447 Jim, in our case, we constantly have stuff going on in the re-use trunk(s), so when a project developer (non reuse area) starts a new proj, they get the latest sanctioned externals def from the sample project area. This will have explicit versions for those portions of the reuse that are under development, and floating (HEAD) for those areas deemed working. Then they just use that def in their project. But on a more troubling note, I did notice doing an update to a folder in the working copy that has a designated revision on the externals def WILL UPDATE TO THE HEAD REVISION if not updated globally from the root. Jim, in our case, we constantly have stuff going on in the re-use trunk(s), so when a project developer (non reuse area) starts a new proj, they get the latest sanctioned externals def from the sample project area. This will have explicit versions for those portions of the reuse that are under development, and floating (HEAD) for those areas deemed working. Then they just use that def in their project.

But on a more troubling note, I did notice doing an update to a folder in the working copy that has a designated revision on the externals def WILL UPDATE TO THE HEAD REVISION if not updated globally from the root.

]]> By: nk http://thinkinging.com/2008/10/21/set-the-revision-of-your-svnexternals-or-else/comment-page-1/#comment-25385 nk Fri, 24 Apr 2009 14:35:09 +0000 http://thinkinging.com/?p=633#comment-25385 Yep that is how we do it also at my workplace. It makes tagging a bit tedious but it is definitely worth it. Someday I'll probably grow tired of it and try scripting it... Unless the fine folks at TortoiseSVN handle it somehow ^^ Yep that is how we do it also at my workplace. It makes tagging a bit tedious but it is definitely worth it.
Someday I’ll probably grow tired of it and try scripting it… Unless the fine folks at TortoiseSVN handle it somehow ^^

]]> By: Gothgod http://thinkinging.com/2008/10/21/set-the-revision-of-your-svnexternals-or-else/comment-page-1/#comment-25350 Gothgod Fri, 09 Jan 2009 11:36:53 +0000 http://thinkinging.com/?p=633#comment-25350 Thanks for the tip! But this should really be handled automatically. What a hassle it is! Thanks for the tip! But this should really be handled automatically. What a hassle it is!

]]> By: Jim Kring http://thinkinging.com/2008/10/21/set-the-revision-of-your-svnexternals-or-else/comment-page-1/#comment-25310 Jim Kring Tue, 28 Oct 2008 18:42:51 +0000 http://thinkinging.com/?p=633#comment-25310 Hi Leif: Thanks for the pointer. That sounds like a very workable approach. Hi Leif: Thanks for the pointer. That sounds like a very workable approach.

]]> By: Leif Suonvieri http://thinkinging.com/2008/10/21/set-the-revision-of-your-svnexternals-or-else/comment-page-1/#comment-25309 Leif Suonvieri Tue, 28 Oct 2008 10:38:24 +0000 http://thinkinging.com/?p=633#comment-25309 A common way to handle this is to first create a "release branch" from current trunk state, and in that branch you set all externals to specific revisions, and if that passes all tests you create the tag from the branch. This way you dont have to touch the externals in the trunk. A common way to handle this is to first create a “release branch” from current trunk state, and in that branch you set all externals to specific revisions, and if that passes all tests you create the tag from the branch.
This way you dont have to touch the externals in the trunk.

]]>