Best Practice: Create tag containing only a subset of files from trunk dir

Hi All,    I'm interested in hearing what the best practice is to manage the following situation I have.    We have a subfolder under trunk, lets call it 'configs' which contains several hundred configuration files, each of which is specific to a particular machine on our network.    We have to perform frequent changes to one or more of these files for weekend releases, so a particular weekend may require changes to five files, another weekend may require changes to 12 files etc. etc.    My initial thought was to allow our team to make the changes to the configuration files within the /trunk/configs folder and then once committed create a new tag /tags/Change#_1234/ which contained only those files which had been redeployed as part of the weekend release.  The tag was so that we could look back over time and see which files had been changed at any particular date, and which other files had been changed at the same time as part of this change (I appreciate that this is kind of held within the revision history under /trunk/configs but I have used tags before to indicate 'production' releases and wanted to do the same here).    The issue I have is that it doesn't seem to be possible to create a tag containing only a subset of the files within the /trunk/configs/ folder. I don't particularly want to create a tag of the entire /trunk/configs folder as this will then contain several hundred config files which haven't changed - which rather defeats the object of creating the tag in the first place.    Can anyone suggest what I should be doing here instead?    tia,  Steve

Last updated 11 years ago

I am also waiting for the solution.  I got a thread on this type of issue svn Tag workflow, some script also there. but not understanding.     can anyone give the solution.

ok just a very quick question so it helps me understand the situation, u want a way of placing any files you commit from the /trunk/configs folder into the tags folder, if this is the case, maybe a post-commit hook script might work where it sends a copy of the commited file to the tags folder, is this something to which you would be after ?

Hi Squeekjjy, Thanks for the response. I've got around my issue by including a 'changelist' file within my SVN tag folder. The changelist file contains only those files which need to be deployed out to the target servers for that particular change, which will be a subset of the total set of files within the tag folder. My Ant script then uses the ChangeList file to identify and deploy the particular files.  It's not perfect but it is working, and I understand why SVN doesn't support 'partial' tags. Having said that, being able to apply a label as I used to be able to do with Perforce would have avoided this situation entirely.  Cheers, Steve

Hi Stevedearl and Squeekjjy, I am new to svn. My task is need to create a tag for only changed files from last build revision to latest revision.  Kindly share the procedure of changelist, the concept of changelist.