Svn2svn – http://kennethxu.blogspot.de/2012/01/svn2svn-copy-and-sync-between-svn.html.
Ever needed to copy/move parts of a repo but svnadmin dump + svndumpfilter failed?
Svn2svn will save your day!
Polarion ALM Tipps #2: avoid svn copy/move
Unless you really want to preserve history, avoid svn copy/move on e.g. workitem-configuration. By using svn copy/move you’ll create connections between projects that will hinder you once you want to move, copy, archive etc. projects.
Instead use svn export + add to e.g. copy files from one project to another.
Svn copy/move is perfectly fine inside a project.
Polarion ALM tipps #1: no single repo
This is the first of a series of blogposts regarding Polarion ALM.
Polarion allows you to have everything – Polarion data (workitems, documents, wiki pages, …) + work artifacts (souce, binaries, documentation, ..) – in one repo, or to separate work artifacts from Polarion data. This feature is called „external repo“.
I strongly recommend external repo because:
- Polarion repo stays small: your work artifacts might explode in pure size and number of revisions.
- Usage of hooks is simplified: you might implement hooks to eg. enforce coding rules. Never apply hooks to Polarion data (unless you really, really know what you’re doing)
- Performance improves: size, hooks will slow down Polarion.
- Transfer of Projects for Investigation, tests etc. will ease: for testing new Polarion release you only need Polarion data.
- External repo can be Git: your developers might love git