It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,862

question asked: Jul 23 '09, 3:02 p.m.
question was seen: 4,828 times
last updated: Jul 23 '09, 3:02 p.m.

Related questions

Selective commit access for some code

0
Shawn Willden (21●2) | asked Jul 23 '09, 3:02 p.m.
I'm evaluating RTC for a project, and we have a perhaps-unusual requirement that I'm struggling with how to implement.

The requirement is that while the whole team (which actually consists of three sub-teams) should have read access to the entire project source code, there is a "protected" subset which only one of the three sub-teams should be able to change. The remainder of the code should be fully accessible to the entire team.

This structure needs to be implemented across multiple streams, too. We'll have a development "trunk" stream, with other streams for client-specific work or other applications, but the same access controls must apply. Also, we may incorporate additional teams that should have access only to these client-specific streams, and they should have no access at all to the "protected" code.

This code protection issue is contractually required, so it needs to be fairly bulletproof.

Can I accomplish something like this? How would I go about it?

Please excuse me if my terminology is off. I'm new to RTC.

2 answers

Most liked answers ↓|Newest answers|Oldest answers

0
permanent link
Shawn Willden (21●2) | answered Jul 23 '09, 4:49 p.m.
This precondition can be configured per component per stream. It is new
in RTC 2.0 and you can read more about it and such scenario at:
http://jazz.net/library/article/215#componentadvisor

Perfect! That's very cool. Thanks a lot!
0
permanent link
Jose Miguel Ordax Cassa (2.4k●4●126●100) | answered Jul 23 '09, 3:35 p.m.
swillden wrote:
I'm evaluating RTC for a project, and we have a perhaps-unusual
requirement that I'm struggling with how to implement.

The requirement is that while the whole team (which actually consists
of three sub-teams) should have read access to the entire project
source code, there is a "protected" subset which only one
of the three sub-teams should be able to change. The remainder of
the code should be fully accessible to the entire team.

This structure needs to be implemented across multiple streams, too.
We'll have a development "trunk" stream, with other streams
for client-specific work or other applications, but the same access
controls must apply. Also, we may incorporate additional teams that
should have access only to these client-specific streams, and they
should have no access at all to the "protected" code.

This code protection issue is contractually required, so it needs to
be fairly bulletproof.

Can I accomplish something like this? How would I go about it?

Please excuse me if my terminology is off. I'm new to RTC.

If I understood your scenario correctly I think the answer is yes. You
should put your protected code into a component or several components
without mixing it with unprotected code in the same component. Then, you
can use the Restrict deliver precondition giving write access to those
components in each stream just for the team area owner of the code.

This precondition can be configured per component per stream. It is new
in RTC 2.0 and you can read more about it and such scenario at:
http://jazz.net/library/article/215#componentadvisor

Hope it helps,

Chemi.

Your answer

Register or to post 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.