It's all about the answers!

Ask a question

Managing Two RTC Project Areas SCM in the same Eclipse Client and preventing out of sync stream issues

David Beange (11135699) | asked Aug 05 '15, 5:04 a.m.
RTC V4.0.6

The issue is concerning SCM and the ability within the same eclispe client to manage both Projects Development within Project Explorer and then deliver baselines from a stream in one PA to a stream in the other.

The account has two  similar Project Areas on the same server.

The components in PA2 were originally  loaded with a snapshot from PA1.

Becasue the Components and their content are identically names when the workspace was loaded they were loaded under different named areas within the same workspace.

         Component A
         Component A

And both structures are available to see and be used in Project Explorer to enable comparison and checking of history as some changes need to be delivered from one PA Component to the other.

However users are frequently getting out of sync errors and need to reload the components and overwrite any local changes that have not yet been checked in or delivered.

Is there a way to avoid this out of sync issue? Is the above even a recognised and recommended way of working?

One answer

permanent link
Ralph Schoon (62.3k33643) | answered Aug 05 '15, 5:31 a.m.
edited Aug 05 '15, 5:32 a.m.
You don't load snapshots. You load repository workspaces. A repository workspace should only be loaded once. If the same repository workspace is loaded in several instances and data checked in in both you get frequent out of sync issues.

For the scenario above, I would strongly suggest to have only one repository workspace loaded at a time. It would be a lot easier and clearer to handle if you use two Eclipse workspaces and load each version only in one of them.
Eclipse has a flat workspace, that means that it has all eclipse projects on the top level - regardless where they are loaded in terms of a folder hierarchy. The SCM component is tied to the Eclipse project. If you load the same component twice into the Eclipse workspace this could cause overlap in the Eclipse projects and that could result in RTC SCm being confused which repository workspace it tracks.

David Beange commented Aug 05 '15, 5:42 a.m.

Hi Ralph, personally I would have been switching between workspaces as required as you say.
I've seen articles on flowing changes cross repositories but they refer to the repositories being on different servers does this apply equally when the repositories are on the same server or is there an alternative way for delivering changes from one repository to another, Flow diagrams?

Ralph Schoon commented Aug 05 '15, 5:50 a.m.

How changes flow is independent of one or multiple CCM.

You basically always load a repository workspace and work on that. You flow the changes from the workspace to a stream (and accept back to integrate), you change flow targets for integration.

You can flow changes from one stream to another provided there are no conflicts in the pending changes view, if a stream has another stream as a flow target. If you have conflicts, you have to resolve them with a repository workspace.

Your answer

Register or to post your answer.