1

There is an Apache 2 licensed tool called Polarion SVN Importer. Has anybody the sources for this and would put them on Github? I guess Apache License gives the right to do this.

The tool can be downloaded at polarion.plm.automation.siemens.com but there are no sources available.

Looks like even if a software is open source, its sources can get lost.

See Recommendation on Tools to migrate from Clearcase to SVN?

Community
  • 1
  • 1
weberjn
  • 1,840
  • 20
  • 24
  • Not that I know of. And I still recommend my approach: http://stackoverflow.com/a/662899/6309 – VonC Mar 21 '17 at 10:26
  • I guess the Polarion tool calls cleartool, so custom scripts would do that too. I have no idea how much work scripts would be, yours aren't on github by chance? – weberjn Mar 21 '17 at 12:30
  • No it is just a matter of listing all the labels (or UCM baselines) we want to export, checkout them in a dynamic view (by changing its config spec: cleartool setcs) and import them in another SCM (in 2017, that would be Git) – VonC Mar 21 '17 at 12:33
  • I have just found https://github.com/charleso and https://therub.org/2013/07/19/clearcase-to-git/ and will have a look at it. – weberjn Mar 21 '17 at 13:04

1 Answers1

1

As the OP weberjn adds in the comments, there are a couple of scripts for Exporting ClearCase to a VCS, but generally it is for the DVCS Git, which works by commits, and not by file version like ClearCase.
(See "What are the basic ClearCase concepts every developer should know?")

But the idea remains the one I described before: for each ClearCase label or UCM baseline, you checkout them and import in your Git working tree.

One easy way is to do:

  • cleartool setcs (a config spec with your label) or cleartool rebase <yourBaseline>,
  • cd /path/to/my/git/repo
  • git --work-tree=/path/to/clearcase/view add .

That last command will automatically detect the files added/modified or removed in your Git repo compared to the previous import.

Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250