Comments on: Tags in Subversion https://www.barneyb.com/barneyblog/2006/10/12/tags-in-subversion/ Thoughts, rants, and even some code from the mind of Barney Boisvert. Thu, 11 Sep 2014 09:58:12 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Barrie https://www.barneyb.com/barneyblog/2006/10/12/tags-in-subversion/comment-page-1/#comment-246016 Barrie Thu, 03 Mar 2011 03:42:18 +0000 http://barneyb.com/barneyblog/?p=186#comment-246016 I did eventually work it out. For anyone else that is interested: 1: Open the Repo Browser 2: Find the trunk of your project 3: Right click and select Copy 4: Enter the path to where you want the copy - it should be under tags eg: Repository\Projects\MyProject\trunk Copy this to Repository\Projects\MyProject\tags\Releasexxx That was it. I did eventually work it out. For anyone else that is interested:
1: Open the Repo Browser
2: Find the trunk of your project
3: Right click and select Copy
4: Enter the path to where you want the copy – it should be under tags
eg: Repository\Projects\MyProject\trunk
Copy this to Repository\Projects\MyProject\tags\Releasexxx
That was it.

]]> By: barneyb https://www.barneyb.com/barneyblog/2006/10/12/tags-in-subversion/comment-page-1/#comment-246013 barneyb Thu, 03 Mar 2011 03:29:40 +0000 http://barneyb.com/barneyblog/?p=186#comment-246013 Barrie, You just need to do `svn mv /path/to/src /path/to/tag` and that's it. The tag path must be a server URL, but the source path can either be a working copy or a server URL. Barrie,

You just need to do `svn mv /path/to/src /path/to/tag` and that's it. The tag path must be a server URL, but the source path can either be a working copy or a server URL.

]]> By: Barrie https://www.barneyb.com/barneyblog/2006/10/12/tags-in-subversion/comment-page-1/#comment-246002 Barrie Thu, 03 Mar 2011 02:26:19 +0000 http://barneyb.com/barneyblog/?p=186#comment-246002 I was looking for step by step instructions on how to create a tag in SVN. This topic seemed to suggest it would do that - but I am still mistified. I was looking for step by step instructions on how to create a tag in SVN. This topic seemed to suggest it would do that – but I am still mistified.

]]> By: sulthan https://www.barneyb.com/barneyblog/2006/10/12/tags-in-subversion/comment-page-1/#comment-244162 sulthan Sat, 19 Feb 2011 13:17:11 +0000 http://barneyb.com/barneyblog/?p=186#comment-244162 Storing development tools in SVN is one of the stupidest ideas I have ever heard. That can work only if the SVN is used by one user. Let's see the following scenarios: 1/ One user on windows, one on linux. Both are using java sources but can't share eclipse binaries. 2/ One user on SVN, has to buy a new computer, different OS, old eclipse on SVN (or other app) won't work (e.g. because old computer was 32bit and the new one is 64bit) 3/ system paths can be different, even localized on windows. Some applications need values in system registry. You can commit your application files to SVN but when you need to checkout to a new computer, the tools won't work. In general, you should commit to your SVN only your own work. Not any external tools that are available from other SVNs or websites. It's better to create a script that will download and install them all and put that script to your SVN (or maybe download some of the binaries to your FTP). Storing development tools in SVN is one of the stupidest ideas I have ever heard. That can work only if the SVN is used by one user. Let's see the following scenarios:
1/ One user on windows, one on linux. Both are using java sources but can't share eclipse binaries.
2/ One user on SVN, has to buy a new computer, different OS, old eclipse on SVN (or other app) won't work (e.g. because old computer was 32bit and the new one is 64bit)
3/ system paths can be different, even localized on windows. Some applications need values in system registry. You can commit your application files to SVN but when you need to checkout to a new computer, the tools won't work.

In general, you should commit to your SVN only your own work. Not any external tools that are available from other SVNs or websites. It's better to create a script that will download and install them all and put that script to your SVN (or maybe download some of the binaries to your FTP).

]]> By: BiGF00T https://www.barneyb.com/barneyblog/2006/10/12/tags-in-subversion/comment-page-1/#comment-218553 BiGF00T Thu, 26 Aug 2010 10:27:54 +0000 http://barneyb.com/barneyblog/?p=186#comment-218553 I agree with yoyar. Although it is nice to have all the stuff checked in, but some of them just bloat the repository and do not really belong there. I've seen people check in a CD image that contained something for a presentation they wanted to hold. Then they deleted it again but did not realize that the trick of version control is that it is still present, just not visible in the latest revision. As a general rule I would say: What can't be generated from what's under version control should be checked in if it is necessary for the program to run. But I wouldn't check in an exe file just because it will change with every time it is compiled. If a compiled program has to be kept for reference/memory/sentimental reasons, then I would not version the file that is produced by the compiler but rather a file which I copy to a place manually or per script only at times when I would like a new version to be stored. Updating binary files over and over will only increase the size of the repository. CD images should (in all cases that I could think of at the moment) not be checked in because it is hard to get them out (export/import + filter). Maybe your EVERYTHING meant just what we said. Checking in everything selfmade is really useful, I agree. When using an IDE, I would like to be able to go back to a revision and open the stuff in my IDE to compile it. I don't want to create a new project and add the source files which I versioned there. But not more than the stuff I need. No log files, no compiled exe files that are the results of my source. Regards, BiGF00T I agree with yoyar.
Although it is nice to have all the stuff checked in, but some of them just bloat the repository and do not really belong there. I've seen people check in a CD image that contained something for a presentation they wanted to hold. Then they deleted it again but did not realize that the trick of version control is that it is still present, just not visible in the latest revision.

As a general rule I would say: What can't be generated from what's under version control should be checked in if it is necessary for the program to run. But I wouldn't check in an exe file just because it will change with every time it is compiled. If a compiled program has to be kept for reference/memory/sentimental reasons, then I would not version the file that is produced by the compiler but rather a file which I copy to a place manually or per script only at times when I would like a new version to be stored.

Updating binary files over and over will only increase the size of the repository. CD images should (in all cases that I could think of at the moment) not be checked in because it is hard to get them out (export/import + filter).

Maybe your EVERYTHING meant just what we said. Checking in everything selfmade is really useful, I agree. When using an IDE, I would like to be able to go back to a revision and open the stuff in my IDE to compile it. I don't want to create a new project and add the source files which I versioned there. But not more than the stuff I need. No log files, no compiled exe files that are the results of my source.

Regards,

BiGF00T

]]> By: barneyb https://www.barneyb.com/barneyblog/2006/10/12/tags-in-subversion/comment-page-1/#comment-201833 barneyb Fri, 08 Jan 2010 18:13:39 +0000 http://barneyb.com/barneyblog/?p=186#comment-201833 yoyar, How is Artifactory different from SVN/CVS? They're both just repositories that store stuff and keep track of the evolution of that stuff across time. yoyar,

How is Artifactory different from SVN/CVS? They're both just repositories that store stuff and keep track of the evolution of that stuff across time.

]]> By: yoyar https://www.barneyb.com/barneyblog/2006/10/12/tags-in-subversion/comment-page-1/#comment-201832 yoyar Fri, 08 Jan 2010 18:08:38 +0000 http://barneyb.com/barneyblog/?p=186#comment-201832 I've seen huge messes created when non source files are checked into cvs/svn etc... I've even see old log files checked in. Source control is for source code. Dependencies can and should be kept in some type of repository (like Artifactory). Deployment tools (maven or ant) put your source code and your deps together to create the application. Keep your source in svn. Keep everything else out of svn. I've seen huge messes created when non source files are checked into cvs/svn etc… I've even see old log files checked in.

Source control is for source code. Dependencies can and should be kept in some type of repository (like Artifactory). Deployment tools (maven or ant) put your source code and your deps together to create the application. Keep your source in svn. Keep everything else out of svn.

]]> By: Jim https://www.barneyb.com/barneyblog/2006/10/12/tags-in-subversion/comment-page-1/#comment-419 Jim Thu, 12 Oct 2006 16:04:54 +0000 http://barneyb.com/barneyblog/?p=186#comment-419 Interesting - I'm moving more and more stuff into SVN but never thought to actually move my applications (CFEclipse) themselves into it... Interesting – I'm moving more and more stuff into SVN but never thought to actually move my applications (CFEclipse) themselves into it…

]]>