Does RTC provide a mechanism for locking a stream?
Thomas Neal (141●1●3●3)
| asked Sep 30 '09, 3:45 p.m.
JAZZ DEVELOPER retagged Oct 06 '17, 4:06 p.m. by Ken Tessier (841●1●7) Is there a mechanism for locking a stream or preventing users from making deliveries to a stream? I can see where we can lock an individual file, but was wondering if it's possible to lock an entire stream from further updates/deliveries?
|
Accepted answer
David Lafreniere (4.8k●7)
| answered Oct 05 '17, 1:14 p.m.
FORUM MODERATOR / JAZZ DEVELOPER edited Oct 05 '17, 5:44 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.
Michael Valenta selected this answer as the correct answer
|
One other answer
tneal wrote:
Is there a mechanism for locking a stream or preventing users from You can do this by adding 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. http://jazz.net/library/article/215#protect_some describes how to protect individual components in a stream, the same approach can be used to lock down the entire stream. Hope this helps, JohnC SCM Server Comments I like all the knowledge that article 215 provides. Thanks.
|
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.