It's all about the answers!

Ask a question

Is there any simple way to lock stream temporarily?

Ashok Sharma (3211118) | asked Jan 22 '15, 3:45 a.m.
edited Oct 05 '17, 6:25 p.m. by David Lafreniere (4.8k7)

Is there any simple way to lock stream temporarily? I searched this forum and found ways like "Create SS then Delete stream" or "Change owner of stream"

Don't we have any simple way like other Source Control tools?

Ashok Sharma

Accepted answer

permanent link
Evan Hughes (2.4k1318) | answered Jan 22 '15, 9:23 a.m.
The easiest way to temporarily modify permissions on a stream is to change the owner to a project/team area that has a very limited membership. The action can be performed with the commandline or rich UIs, and is very quick. It has the benefit of assigning a consistent set of behaviours to the stream, so that it can remain read-only, or modifiable by some subset of users. 

There are alternatives, but they depend on your use case. Can you tell us a bit more about what you're trying to do?

If you want to lock streams regularly (during the endgame of a release, for example), you may want to consider assigning behaviour or permissions to iteration types. 
David Lafreniere selected this answer as the correct answer

David Lafreniere commented Oct 05 '17, 6:25 p.m.

Also, 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.

Your answer

Register or to post your answer.