Browsing projects by Tag(s)

Select a tag to browse associated projects and drill deeper into the tag cloud.

Showing page 1 of 1

cc2svn tool converts ClearCase view files with all history and given labels to SVN dump. The dump can be loaded by SVN using 'cat svndump.txt | svnadmin load' command. Features:transfers history of changes for files saving the date, author and comment for each revision converts ... [More] all/some/none branches (configurable) converts all/some/none labels (configurable) incremental dump mode retry/ignore failed CC commands cache for ClearCase files tested on Linux/Solaris Main points:The tool uses the current ClearCase view to list the CC history (ct lshi -rec) then it goes through the history and processes each record. That means that the tool does not transfer those files that are not visible from the current CC view. However the tool transfers all CC labels to SVN tags correctly. For that in the second phase it sets config_spec of the current view to match the label (element * LABEL) for each given label and checks that no files are lost during the first phase. WARNING: Side effect - the tool changes the config_spec of the current working ClearCase view. Do not use the view during the tool work. All branches except the /main are created using 'svn cp' command basing on the CC parent branch. There is a difference in creating the branches in ClearCase and SVN: SVN copies all files from parent branch to the target like: svn cp branches/main branches/dev_branch ClearCase creates the actual branch for file upon checkout operation only. In other words the tool can't guarantee the content of /branches will be exactly like in ClearCase. But the tool guarantees the labels are transferred correctly. The tool uses cache directory to place ClearCase version files there. The cache speeds up the transfer process in many times in subsequent attempts (up to 10 times). It may be recommended to start the tool 2 days before the actual transfer loading all files to the cache. So only new versions appeared during these days will be retrieved from ClearCase in the day of the transfer. Actually the tool caches any data retrieved from ClearCase including the history file. The tool provides the possibility to retry/ignore any ClearCase command if error occurs. The tool will put empty file to the cache if you ignore ClearCase retrieving operation error. Timing: CC repository of 5 GB (~120.000 revisions) is converted in ~1 hour using the pre-cached files. Options:# The cleartool command full path CLEARTOOL = "/usr/atria/bin/cleartool" # The root directory for conversion # The tool will launch ct lshi -rec there and will convert all files found below this directory CC_VOB_DIR = "/vobs/MY_VOB_DIR/path/to/root" # The tool uses cache directory to place ClearCase version files there. The cache speeds up the transfer process # in many times in subsequent attempts (up to 10 times). It may be recommended to start the tool 2 days before the # actual transfer loading all files to the cache. So only new versions appeared during the 2 days will be retrieved from # ClearCase in the day of the transfer. # NOTE: Make sure there is enough space in cache directory. CACHE_DIR = "/var/tmp/cc2svn_cache" # The tool can not track the history of ClearCase symbolic links # This is a workaround for this. When the tool finds the symlink record in CC history # it creates the link in the given branch. If the branch does not exist at the time # the link was created, the tool skips the link. PUT_CCLINKS_TO_BRANCH = "main" # The tool may add some svn properties to the files depending on the file extension # config.autoprops contains the basic mapping for extension -> svn properties # You can add or change your mapping there # The syntax is: shell-pattern = svnproperty=value;svnproperty=value;... # the space between shell-pattern and equal sign '=' is mandatory SVN_AUTOPROPS_FILE = THIS_FILE_DIR + "/config.autoprops" # If CC_LABELS_FILE is not defined, the tool will convert all labels it finds in history of the current view # If CC_LABELS_FILE is defined (recommended), the tool will transfer only those labels mentioned in file # If you do not want to transfer any labels, specify an empty file # file must contain one label per line, example: # LABEL_1 # LABEL_2 CC_LABELS_FILE = THIS_FILE_DIR + "/labels.txt" # If CC_BRANCHES_FILE is not defined, the tool will convert all branches it finds in history of the current view # If CC_BRANCHES_FILE is defined, the tool will transfer only those branches mentioned in file # If you do not want to transfer any branches, specify an empty file # file must contain one branch name per line (without slashes), example: # main # user_dev CC_BRANCHES_FILE = THIS_FILE_DIR + "/branches.txt" # If the tool finds the size of the file in cache is zero, it may try loading the file from ClearCase again. # This is to make sure zero size is not due to previous unsuccessful retrieving attempt. CHECK_ZEROSIZE_CACHEFILE = True # Should svndump contain the command to create SVN /branches and /tags directory or not # It will be an error if you try loading the dump with such command to SVN repository containing these directories SVN_CREATE_BRANCHES_TAGS_DIRS = False # SVN dump output file created by the tool SVN_DUMP_FILE = "svndump.txt" # ClearCase history file created by the tool HISTORY_FILE = "cchistory.txt" # DUMP_SINCE_DATE activates incremental dump mode. This should be used after the full dump mode only. # The idea is: you convert cc2svn on the day X without using this option, working in svn and ClearCase simultaneously # (do not commit the same changes in svn and CC), then create incremental dump using DUMP_SINCE_DATE=X option. # Dump will include revisions with date > DUMP_SINCE_DATE (strict greater) only. # Note: SVN_CREATE_BRANCHES_TAGS_DIRS is ignored in incremental mode # Date format is YYYYMMDD.hhmmss (the same as CC is using). DUMP_SINCE_DATE = "20080921.175059" [Less]

0
 
  0 reviews  |  0 users  |  659 lines of code  |  1 current contributor  |  Analyzed 4 days ago
 
 
 
 

Creative Commons License Copyright © 2013 Black Duck Software, Inc. and its contributors, Some Rights Reserved. Unless otherwise marked, this work is licensed under a Creative Commons Attribution 3.0 Unported License . Ohloh ® and the Ohloh logo are trademarks of Black Duck Software, Inc. in the United States and/or other jurisdictions. All other trademarks are the property of their respective holders.