It's all about the answers!

Ask a question

How to Lock a stream

Leo Sager (312) | asked Mar 15 '10, 1:21 p.m.
edited Oct 05 '17, 6:46 p.m. by David Lafreniere (4.8k7)

I was trying to see if a whole stream can be locked (like locking a branch). There is this techote:

It says the version is 1.x, but not 2.x, so I was wondering if the answer is different in 2.x. Also, I dont understand how to do what they say to do. I need some explicit instructions that even my non-tech Mom could do. :)

Accepted answer

permanent link
David Lafreniere (4.8k7) | answered Oct 05 '17, 6:52 p.m.

In RTC 6.0.2 we added a feature that lets you lock streams and components to prevent deliveries to the files in those streams or components. Stream and component locks work in a similar manner to file locks but apply to the entire stream or the entire component in a stream. When a stream or component is locked, any attempted deliveries by users who do not own the lock will fail with an appropriate error message. The user that holds the lock can still perform deliveries to the stream. A lock does not only prevent deliveries, it also prevents any operation that affects the files in the locked component or stream. For example, a component replace is also prevented.

-New & Noteworthy Mention:
-Stream/Component Locking Demo Video:
-SCM Command Line Client 'set lock' command:

Prior to 6.0.2, you could do what is described in the tech note by changing the owner of a stream to a Team area or Project area in which nobody has deliver rights (this is also clarified by Ralph in his answer). You can change the owner of a stream by opening the stream in an editor in RTC Eclipse for example. Also, another approach might be to add a deliver advisor in the process spec to restrict deliveries to particular streams. By protecting your stream by particular roles or users, you can effectively lock the stream down.
"" describes how to protect individual components in a stream, the same approach can be used to lock down the entire stream.

Michael Valenta selected this answer as the correct answer

One other answer

permanent link
Ralph Schoon (63.0k33645) | answered Mar 16 '10, 3:44 a.m.
edited Oct 05 '17, 6:48 p.m. by David Lafreniere (4.8k7)


the tech note still applies. The idea is to make the stream owned by a team that does not provide delivery permissions. In the Library you can find describing how permissions are handled.

the idea of the tech note is in general to remove permissions to deliver for everyone. There are at least two ways to achieve that.

1. You can remove the permission to deliver for everyone in the team the stream is owned by.
2. You can have a special team that does not grant delivery permissions and make the stream owned by a team. The effort to do this and especially to reverse it is very low compared to solution 1 there fore it is proposed in the tech note.

To do 2 right open the stream. On the Stream Editor look for the Team owning the stream. On said editor select a team prepared with no delivery permissions (deselect the permission in the process customization of said team) as new owner to lock the stream. To reverse change the owner of the stream back to the desired team.

It is not rocket science and your Mom could do it, provided you allow her to play with RTC. 8-)

Leo Sager commented Mar 16 '10, 7:28 a.m. | edited Oct 05 '17, 6:48 p.m.

AH!!!! Your explanation was much more clear than the technote! Thanks so much!!!! As for my Mom, think I'll keep her to the web version so she can see pretty graphs. :D

Your answer

Register or to post your answer.