Restrictions to Load a component into sandbox in Jazz Source Control?
Hi All,
I don't want users to Load a particular component from their private Jazz Repository workspace into the sandbox (Local Workspace). Is there any way available in Rational Team Concert to restrict users from loading particular repository workspace component only into their sandbox. I'm not aware of any preconditions or permissions for such, if any. Can you please suggest me some way around? |
Accepted answer
If users don't load a component into their development environments, I suggest you remove it from the stream that they contribute to. That way they will receive a 'component removal' notification that will suggest that they should remove the component and new repository workspaces won't contain the component.
One reason you might want a component in a stream is because you need it for a build. If that's the case, then you can add the component to your build workspace and set the flow target to be another stream that holds the component.
If that isn't possible, you can suggest to users that they load with a specific load rule file that excludes the component you don't want to load.
Tanmay Shirnalkar selected this answer as the correct answer
|
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.
Comments
Since it is their Jazz Repository workspace, and their sandbox, why would you want/need to prevent them from loading whatever they want into it?