Page 1 of 1

Branching with external repository storage

PostPosted: Wed Jan 19, 2011 7:18 am
by klonk
Hi-
How does Teamwork Server manage branching when its repository is stored externally?
Does it use ClearCase /Subversion to create branches or are the branches managed internally in Teamwork Server?

Thanks!
-klonk

Re: Branching with external repository storage

PostPosted: Mon Jan 24, 2011 4:14 am
by mantbaln
Hello,

Teamwork Server uses VCS branching. Note that you can't make any manual modifications in repository used by Teamwork Server. The benefit of branching is that you can see history of project file.

Re: Branching with external repository storage

PostPosted: Mon Jan 24, 2011 5:58 am
by klonk
mantbaln wrote:The benefit of branching is that you can see history of project file.


Hi,
could you explain this a bit further, please?

I understand Teamwork Server kept track of the project history regardless of branching? Is there a difference between VCS branching and native repository branching (other than the underlying storage)?

Best regards
-klonk

Re: Branching with external repository storage

PostPosted: Mon Jan 24, 2011 7:34 am
by mantbaln
Hello,

In Native and VCS repositories branching is handled in different way. When integrated with VCS Teamwork Server does not keep any project version history. All information is loaded from VCS file history.

Please describe your situation that we could suggest the best solution.

Re: Branching with external repository storage

PostPosted: Mon Jan 24, 2011 9:37 am
by klonk
Hi,
The situation is this:

Where we are now:
    We have an existing Rational Rose model with links to external Word documents. Authentication is done on ClearCase/OS level via LDAP. Both the model and the documents are maintained in the same ClearCase VOB. When a release is complete the model and documents are labeled in ClearCase. To support multiple releases ClearCase branches are used.

Where we want to go:
    We want to maintain the model in MagicDraw with links to external Documents. Authentication should be done via LDAP. Ideally we would be able to label and branch both the model and documents in one single ClearCase VOB.
    However, as far as I know, this is not possible, because Teamwork Server controls branching itself and should not be interfered with. Is this right?
    Any alternative suggestions?

Best regards
-klonk

Re: Branching with external repository storage

PostPosted: Tue Jan 25, 2011 8:00 am
by mantbaln
Hello,

Teamwork Server can authenticate via LDAP but there is no support for external documents. Branching works in file level instead of folders those there is no possibility to insert unrelated files.