It's all about the answers!

Ask a question

Repository Workspace Team Ownership?


Joel Lonneker (39916) | asked Nov 15 '11, 2:32 p.m.
In the RTC 3.0.1 environment, is there a reason why Repository Workspaces can only be owned by individuals and not teams?

Thank You,

Joel

3 answers



permanent link
Anthony Kesterton (7.5k5175136) | answered Nov 15 '11, 4:32 p.m.
JAZZ DEVELOPER
In the RTC 3.0.1 environment, is there a reason why Repository Workspaces can only be owned by individuals and not teams?

Thank You,

Joel


Hi Joel

A repository workspace is a mirror image of the sandbox (local workspace) on your client machine. RTC keeps the two in sync so that when you do a checkin - it copies the updated files from your local machine to *your* space on the server - the repository workspace.

Having multiple people work against the same repository workspace would not work given the above. You would be forced to reconcile any changes as part of a checkin, rather than do this when you deliver your changes to the stream (which is the "shared" area).

This is quite a different model compared with most SCM systems.

anthony

permanent link
Joel Lonneker (39916) | answered Nov 15 '11, 5:30 p.m.
In the RTC 3.0.1 environment, is there a reason why Repository Workspaces can only be owned by individuals and not teams?

Thank You,

Joel


Hi Joel

A repository workspace is a mirror image of the sandbox (local workspace) on your client machine. RTC keeps the two in sync so that when you do a checkin - it copies the updated files from your local machine to *your* space on the server - the repository workspace.

Having multiple people work against the same repository workspace would not work given the above. You would be forced to reconcile any changes as part of a checkin, rather than do this when you deliver your changes to the stream (which is the "shared" area).

This is quite a different model compared with most SCM systems.

anthony

Thank You, Anthony!

permanent link
Geoffrey Clemm (29.7k23035) | answered Nov 16 '11, 12:23 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
A workspace is intended for use by an individual, while a stream is
intended for shared use by a team.

Why would you want a workspace to be owned by a team?

Cheers,
Geoff


On 11/15/2011 2:38 PM, paavo26 wrote:
In the RTC 3.0.1 environment, is there a reason why Repository
Workspaces can only be owned by individuals and not teams?

Thank You,

Joel

Comments
Edward Lenoir commented Aug 08 '12, 5:25 p.m.

Geoff - Joel was asking this based on a question I asked him last year - but he forgot to mention that the question is about a BUILD workspace. We do have a single ID that we use for the build workspace, but it is a bit of a pain to maintain the build when only an admin can make changes to the build workspace. What we are wondering is if there has been much/any demand for a shared ownership of the build workspace for management purposes. I.E. we have pretty much the capability to manage builds definitions and other build aspects EXCEPT for anything that has to do with the workspace.

Your answer


Register or to post your answer.