Migrating project from Synergy 6.5 to RTC
Hi ,
We are plan to migrate from Synergy Cm 6.5 projects to RTC . our project structure include : 220 directories in the root 70,000 objects ( source files,Visual studio files, ) currently the we do not share any projects with others group. What is the correct structure I should migrate this project to RTC ? Dose each of 220 root directories should be components ? Can I do one component for all project ? Thanks, Mickey |
10 answers
Geoffrey Clemm (30.1k●3●30●35)
| answered Apr 23 '11, 8:44 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Normally, you'd put multiple related projects into a component.
What matters more than how many total components you have, is how many components you would need to load into a workspace for development or a build. In particular, 220 components in a workspace is more than I'd normally recommend (largely because of the impact on the usability of the GUIs that manipulate those components). Conversely, I'd normally recommend fewer than 70,000 objects (files/directories) in a single component. Is there some natural grouping of the projects that would keep the component size below 50,000 objects? Cheers, Geoff On 4/23/2011 5:23 PM, mickey_roash wrote: Hi , |
|
Hi Geoff,
I want to correct my input ,we have 62 directories in the root and 220 Synergy projects After thinking about it for a while , some of the project are not necessary for build our executable and they can set to different component, this mean we can decrease the objects that developers need to 40,000 . Is that acceptable to have in one component ? What is the impact having many objects in one component (taking in account that the RTC Server will not hosted in local site) ? Can we have even 3~5 components and still keeping the same directories hierarchy as we have today? Thanks, Mickey Normally, you'd put multiple related projects into a component. Hi , |
Hi,
i wonder that do RTC has the facilty for migration from synergy with history. if not then i beilive you are planning only the latest file?? i am not sure but i would definitely like to know your plan in details because i am on the same boat. Thanks |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Apr 30 '11, 12:11 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The main advantage of loading all your directories into one component is
that you can freely move files and folders anywhere within the component. The main advantage of creating multiple components is that you can create new configurations by selecting specific baselines of each component. WRT keeping your same directory structure, as long as you add some number of your 62 directories into the top level of each component, it will be reasonably easy to recreate your current directory structure in your file area sandbox (both in manually loaded developer workspaces, and in automatically loaded build workspaces). Cheers, Geoff On 4/29/2011 7:38 PM, mickey_roash wrote: Hi Geoff, |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered Apr 30 '11, 12:13 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
A Synergy Synchronizer (based on the technology used for the ClearCase
Synchronizer) is under development. Stay tuned for details on functionality and projected release date. Cheers, Geoff On 4/30/2011 4:53 AM, manoj.panda wrote: Hi, |
A Synergy Synchronizer (based on the technology used for the ClearCase Hi, Dose Synergy Synchroniser is migration tool ? Can I used it for migrating my last development release to RTC stream ? Thanks, Mickey |
Hi all,
I am also involved in migrating from Synergy 6.5 to RTC. Maybe we should form a support group. Or, more realistically, a separate forum thread, if there are enough to reach critical mass. I would be happy to share what we're learning along the way, and hopefully also learn from what others are doing. We've got a lot of code in Synergy 6.5, with a lot of baselines and individual object history. We don't need everything migrated over to RTC, but we do need a lot, in order to investigate and resolve issues that come up across different Synergy releases (i.e. branches). I am interested in knowing how others are approaching the history migration challenges. Regards, Scott |
|
Geoffrey Clemm (30.1k●3●30●35)
| answered May 03 '11, 11:12 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Because the Synergy Synchronizer is based on the ClearCase Synchronizer
technology, you can get an idea about what kind of functionality the Synergy Synchronizer is likely to provide by reading up on the ClearCase Synchronizer (provided in the RTC on-line help documentation). But note that the Synergy Synchronizer may drop some ClearCase Synchronizer features, and may add new features, so this is just to give you an idea of what kind of functionality is likely to be available. Cheers, Geoff On 5/3/2011 12:38 PM, mickey_roash wrote: gmclemmwrote: Dose Synergy Synchroniser is migration tool ? Can I used it for migrating my last development release to RTC stream ? Thanks, Mickey |
How did this migration of project(s) from Synergy 6.5 to RTC work out? There was no update as to success/issues/workarounds and I would like to know if it was done with the Synergy Synchroniser tool and would appreciate an update.
|
Hi All,
Any solution on migrating synergy source code to RTC.
How to handle the history/baseline migration from Synergy to RTC.
Thanks
Deepan
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.