It's all about the answers!

Ask a question

Rational Team Concert Stream Component Permissions

Samir Shah (1623) | asked Mar 07 '14, 9:05 a.m.
 My development team currently has 2 development streams. We want to create a third stream (which is essentially a duplicate of another stream) for the purpose of post-build deliver. Essentially, we want to deliver changes to the second stream.

The issue we have is with the permissions on the components. We have noticed that if you change the permissions on the component in the duplicate stream, then the permissions on the component on the main stream also change. 

What we are trying to accomplish is to have our main stream where check in and delivery occur, and a secondary stream that only gets updated by post-build delivery (and only the build engineer has access to that stream). From what we see, this is not possible. How can we accomplish this with RTC?

2 answers

permanent link
Geoffrey Clemm (30.1k33035) | answered Mar 07 '14, 1:25 p.m.
The permissions on the component determine "read access" to the change sets and baselines in that component.   This is specified on the component itself, and so any change here globally affects read access to that component.   On the other hand, write access to a component (which is what you are looking for here) is controlled on a per-stream basis.  In particular,  look at the "Change Set Delivery to Components in a Stream" precondition on the "Source_Control -> Deliver(Server)" operation.

permanent link
Evan Hughes (2.4k1318) | answered Mar 12 '14, 11:07 a.m.
I would opt to use process preconditions as Geoff suggested. The most appropriate would be Restrict Change Set Delivery to Components in a Stream

You could also put the post-build stream in a different team area. The other team area would only have the users that are allowed to deliver to that stream, and they would have their Source Control permissions set appropriately. 

Your answer

Register or to post your answer.