How to work with multiple repositories?
Is there a recommended way of working with multiple repositories?
I would have liked to be able to have components from several repositories in my repository workspace, but Jazz (Beta 2a) doesn't seem to allow that.
I guess that I could have one repository workspace for each repository but that seems quite awkward.
I would have liked to be able to have components from several repositories in my repository workspace, but Jazz (Beta 2a) doesn't seem to allow that.
I guess that I could have one repository workspace for each repository but that seems quite awkward.
5 answers
There currently are no cross-repository data structures, so yes, you
would need to have a repository workspace for a given repository in
order to download versioned information from that repository.
Cheers,
Geoff
karasiuk wrote:
would need to have a repository workspace for a given repository in
order to download versioned information from that repository.
Cheers,
Geoff
karasiuk wrote:
Is there a recommended way of working with multiple repositories?
I would have liked to be able to have components from several
repositories in my repository workspace, but Jazz (Beta 2a) doesn't
seem to allow that.
I guess that I could have one repository workspace for each repository
but that seems quite awkward.
Can you detail your pain points?
Since what I was working on was small, and since I had total control, I ended up moving everything into a single repository. I no longer remember what all the problems were.
However, if I look at the way we work today (with CVS) we have many repositories. I think this is mostly because of "ownership/control" reasons, not technical reasons. I don't see the forces that drove us to multiple repositories going away any time soon.
We have similar reasons to need multiple repositories (ownership/control). Scalability might be an additional reason.
SCM changesets are the most important item that should be shared between those repositories.
Also within a single repository it is likely that groups might want to share changesets between streams in two different projects.
A possible (and clean) solution that would probably work for us would be a jazz-to-jazz connector, similar to the clearcase-to-jazz connector.
(I entered a enhancement-workitem for this: 47880)
regards
Daan.
SCM changesets are the most important item that should be shared between those repositories.
Also within a single repository it is likely that groups might want to share changesets between streams in two different projects.
A possible (and clean) solution that would probably work for us would be a jazz-to-jazz connector, similar to the clearcase-to-jazz connector.
(I entered a enhancement-workitem for this: 47880)
regards
Daan.
You can currently host different projects with in the same repository with different permission models from a ownership/control standpoint. Having a single repository of this nature allows the sharing of change sets across projects a lot easier to manage. There is a slight paradigm shift here in the context of CVS and Rational Team Concert