Locking down streams
Hi, I have 2 streams in src control each with their own single component, one for devt, the other for release. Release contains a folder per release, and each folder contains files for that release. I want to set something up so that for each release (ie. folder) all developers can add files (ie.deliver, typically via web ui) to it until the release is ready, at which point it is locked down to all except admins. Can't think of an easy way to do this, if anyone can help. Thanks
Sola |
One answer
Geoffrey Clemm (30.1k●3●30●35)
| answered Jul 11 '11, 12:53 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
The way you lock down a stream is through the Permissions for that
stream. In particular, you would specify that nobody has permission to deliver to that stream. (You specify this in the Process Configuration page for the project/team area that owns that stream). A couple of comments on your example though: If you have one stream for development, and one stream for release, then assumedly, they each have the same component(s) in each stream, so that you can deliver changes from the development stream to the release stream. If you have multiple active releases, you would have multiple release streams (one per release), not multiple folders in a single release stream (each stream contains at most one version of a given file). Cheers, Geoff On 7/11/2011 10:38 AM, solajazz wrote: Hi, I have 2 streams in src control each with their own single |
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.