I am just curious what data or info.
I have to collect to migrate the code from mainframe to ClearCase.
Any tutorial will be really helpful.
If you are speaking about data without history (just a bunch of files), then all you need is to:
be able to export that group of files
import it in a ClearCase view (typically using clearfsimport)
See:
"How to use clearfsimport to import files into an empty VOB" and
"How can I use ClearCase to “add to source control …” recursively?"
Related
I recently started usage of clear case tools for maintenance of code in better way. But after some days my "Company" forgot to take licence from IBM as result I cannot CHECK-IN my code into clearcase. To continue my coding i created a separate folder in other drive and copied code solution in that folder. I and my colleague modified around "9865" files of solution within "45" working days. Now a "Company" borrowed a licence for me and I able to access code clear case tool successfully.
Problem is:
How to check in my "9865" files into clearcase in better way?
I tried:
Copied all solution into Snapshot view folder location. but, all
changed files are showing "hijack".
The best way is to use clearfsimport: that will automatically checkout, and import your 9865 in one command.
Make sure to update your snapshot view first, in order to restore its original content.
Then clearfsimport those files.
clearfsimport -preview -rec -nset /path/to/sourceDir\* </myview/VOB>
The clearfsimport command will detect the files added or modified, and do the checkouts for you.
If you are using an UCM view, set an activity first.
The source from where clearfsimport does that copy can be any regular folder.
I need some help on how to collect all information from ClearCase and tar or zip it, and store it in a provided space. we have migrated major baselines from ClearCase to different SCM tool .But we still have ClearCase. we want to capture all version, change, baseline, etc (basically capture everything but not the SCM tool itself) and zip it or put it in a flat file or so. this is just for historical purposes, so that tomorrow if someone wants to know what was in the ClearCase then they can see. so ,is there any idea?
The reason this doesn't exist (as far as I know) is in the nature of ClearCase (compared to a revision-based VCS tools).
It is a file-based VCS:
You create a new version for each file you change (instead of a unique repository-wide revision)
You create a label on each file you want to label (instead of a tag referring to a revision or a commit)
You create a branch for each file modified in that branch (instead of a single directory for SVN, or branch for other VCS)
...
That means you wouldn't simply export revisions/labels/branches with ClearCase. You would export them for each file: it doesn't scale well and would take too much time and space.
Migrating major baselines is sensible course of action that I have recommended before.
But for the rest, I always put a ClearCase instance as a way to explore the full history/events in case in is needed, while the recent history is managed in the new VCS tool.
Storing that as a flat file you could read without ClearCase isn't, again as far as I know, available.
Hence my previous "vobstore-reformatvob" proposition.
I'm trying to import a full RTC repository into a ClearCase VOB. I have tried using clearfsimport but it seems like it only take the latest version of the files. Is there any way to import the code while retaining history (comments, renames etc.)
Such an import should be done component by component into a UCM components Vob, and not into a plain Base ClearCase Vob.
UCM components (and streams) map quite nicely with the RTC component and Streams, but with clearfsimport, the import process would still be:
manual (in that you would have to select each RTC baseline you want to see in order to 'clearfsimport' them)
done for baselines only (it would be too long to import all the RTC revisions)
without metadata like merges or rename
In theory, it is possible (but I haven't tested it), through one of the ClearCase-RTC connectors called "ClearCase Synchronizer".
ClearCase Synchronizer is a two-way data replication between ClearCase and Rational Team Concert source control.
You can choose a UCM stream or a ClearCase branch and set up synchronization with a stream of Rational Team Concert source control.
It leverages Jazz Team Build, and you can run the synchronization on a scheduled basis or as you request.
This will provide flexibility to enterprise customers to let subset of teams to choose SCM tools to work with, and yet manage all the latest source code by single SCM repository.
See "Using the Rational ClearCase Synchronizer and Importer".
But I don't know how well it can work (or if it works at all) with an empty UCM component on one side, and a full-history RTC component on the other.
I'm attempting to import a clearcase project into rtc source control and I'm following this tutorial :
https://jazz.net/library/article/50
Is this tutorial sufficient ? When code is checked into clearcase will it also be checked into rtc source control automatically?
Any common pitfalls / online tutorials welcome
Honestly, for a couple of baselines, I simply create an import RTC stream (ie, a stream dedicated for imports), and I manually copy a few baselines, selected from a dynamic view (which has a config spec you can easily change in order to select the appropriate baseline)
Whatever the tool you end up using for this import, the common pitfalls are:
import directly in an RTC Stream used for development: it is best to isolate the import in a dedicated Stream, which will allow you to start working on one of the imported baselines in an RTC Dev Stream, while completing further round of import later in time in the Import Stream.
import all the history (instead of only a few selected baselines)
import without cleaning first (ie you might realize you stored in ClearCase quite a few binaries, libraries or other generated files that you might want to ignore, through a .jazzignore file for the import)
import without refactoring the components: a UCM ClearCase component might have been use over the year as one giant bucket for multiple projects codebases.
The import to another VCS is the good time to split it into several smaller components.
Shutting down ClearCase completely after the import: since you don't import all the history and not all the owner for each versions, you might need to consult back from time to time the history stored in ClearCase.
Don't forget to lock the vobs though, to ensure a read-only access.
Is it possible?
Exporting sources from ClearCase?
The surest way is a snapshot view on a dedicated workstation: since a snapshot view has its storage (the equivalent of the .svn directories) outside the said view, that means the resulting directory is clean.
Then you can take this tree, compress it and transfer it whenever you want, (like a workstation without any VCS)
Use a snapshot view. Update the config spec in such a way that it selects the latest version of all elements from the main branch.
Copy the folder recursively to another folder say c:\svntemp
Import the contents in c:\svntemp\ in to SVN.
For each branch that you have you need to follow this procedure