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

RE: Tag only the changed list

From: Muthu Gopal <muthuboy_at_hotmail.com>
Date: 2005-03-31 07:25:14 CEST

Thank you Robert.

Here is the reason for my request on creation of tag based on changedset. As I mentioned earlier, in our org. the development of code is done by one team, while the compilation and development of the binaries are done by another team. The compilation team would pick-up sources only from the subversion repository.

The development team commits the changes in the repository for each change request or defect fix. So let's say there are 3 defects affecting 15 files ( 5 files each),3 commits would be done by the development team. Out of these 15 files, 6 may be from java folder,4 may be shell folder and another 5 from jsp folder. When they handover the sources, they ideally create a tag and ask the compilation/deployment team to pick-up sources using that tag. Since the compilation/deployment team would need only the files that are changed after the last deployment (but in the same directory tree structure), having the entire source set in the new tags  would mean, the compilation team must execute the svn diff/log commands to pick up sources, instead of the straight forward svn update and windows copy.

Secondly the development team instead of handing over all the changes made for 3 commits, may like to handover the changes made for the 1st commit and the changes made for the 3rd commit (if they are mutually exclusive, which is the real scenario in our org) in one shot to the deployment team, leaving out the changeset of the 2nd commit. If the development team creates a tag (using svn copy) after the 3rd commit, they would get the entire repository in the new tag.  The svn diff/log would also have changes made for the 2nd commit.

The commands Robert has listed are fine, but I would require the files in the tags folder with the same directory structure as in trunk ( something like /tags/mytag/java/<specific but not all java files>, /tags/mytag/jsp/<specific but not all jsp files>, etc)

I have read something related to this  under the "Complex tags" section of the subversion book. However it's not very clear on how to handle this situation. Moreover it's still addresses only the full release deployment and not incremental.


>From: Robert Hunter <robert.hunter@gen-i.co.nz>
>To: users@subversion.tigris.org
>CC: Muthu Gopal <muthuboy@hotmail.com>
>Subject: RE: Tag only the changed list
>Date: Thu, 31 Mar 2005 11:22:26 +1200
>Muthu Gopal wrote:
> > In the trunk folder, I have totally 1000 files. My
> > developer keeps making changes and creates revisions in
> > the trunk say 8,9 and 10. And each of these revisions he
> > modifies just 3 files i.e. totally 9. Now he likes put
> > these 9 files ( modified in 8,9 and 10) alone in a tags
> > folder and handover to another entity for
> > build/deployment.
> >
> > Subversion allows me to create a tag as of 10 revision but
> > would copy all the 1000 files to the tags folder. I want
> > just these 9 files - the changed files in these 3
> > revisions - to be copied to the tag.
> >
> > Is it possible?
>Sure it is. I'm not sure I'd call this a "tag", really, but
>you can call it what you like. :-)
>Just copy the files, as you like them, to a directory.
>You can use something like:
>$ svn mkdir $REPOS/tags/my-tag
>$ svn copy $REPOS/trunk/file1 $REPOS/tags/my-tag/
>$ svn copy $REPOS/trunk/file2 $REPOS/tags/my-tag/
>$ svn copy $REPOS/trunk/file3 $REPOS/tags/my-tag/
>This would create a new revision for each copy, though,
>so it would probably be better to do something like:
>$ svn mkdir $REPOS/tags/my-tag
>$ svn checkout $REPOS/tags/my-tag
>$ svn copy $REPOS/trunk/file1 .
>$ svn copy $REPOS/trunk/file2 .
>$ svn copy $REPOS/trunk/file3 .
>$ svn commit
>By the sounds of it, however, you don't need to bother
>with creating such a complex copy. If the files are
>to be handed to another entity, then you can get the
>names with:
>$ svn log -v -r8:10
>I hope that's some help :-)
>Robert Hunter
>This communication, including any attachments, is confidential.
>If you are not the intended recipient, you should not read it
>- please contact me immediately, destroy it, and do not copy
>or use any part of this communication or disclose anything about it,
>Thank you.
>Please note that this communication does not designate an information system
>for the purposes of the Electronic Transactions Act 2002
--------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org For additional commands, e-mail: users-help@subversion.tigris.org Received on Thu Mar 31 07:27:46 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.