Creating a storage model that references project areas in di
Is it possible to define a storage model that references project areas
that reside in different repositories? I need to build a tree structure where the branches of the tree closest to the root are completely independent of any project area, but allow a branch to be created that is tied to a project area that may be in the same repository, or in a repository on a server half the way around the world. Any children of the branch tied to a project area are also tied to that project area. Is anything like this possible? Are there any examples of how I might go about doing this? Bryan |
One answer
Bryan Hunt wrote:
Is it possible to define a storage model that references project areas You can use URI references with ILink's. If you want to model it explicitly, you could add a String field to a model element (with perhaps another String to represent a label). I have done this at times, and I have also added a UUID representing the repository root (so I have the ability to heal broken links when servers get renamed or are multihomed). Not all users may not always be able to contact the other server (or authenticate against the other server), so your component may need to figure out how to survive when this information is not available. JohnC SCM Server |
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.