HOw to share the source code between different project areas
Hi,
We have two Project Areas..
PA1 and PA2
we would like to share the source code between streams in different project areas..
HOw are we going to restrict the users in folder level.
due to audit issue we are planning ro Rename the Project area, Component, stream and Repository workspace in the production evnrionmnet..
Please let us know the impact..
Regards,
sriramak
We have two Project Areas..
PA1 and PA2
we would like to share the source code between streams in different project areas..
HOw are we going to restrict the users in folder level.
due to audit issue we are planning ro Rename the Project area, Component, stream and Repository workspace in the production evnrionmnet..
Please let us know the impact..
Regards,
sriramak
5 answers
Thanks for the info..
Please let me know the inputs for below topics...
HOw are we going to restrict the users in folder level.
due to audit issue we are planning ro Rename the Project area, Component, stream and Repository workspace in the production evnrionmnet..
Folder level restrictions are not available in 3.x this is planned for 4.x. Restrictions/permissions can be done on component, stream.
I am not sure what the audit issue is due to missing context, but I believe if a component is renamed it is renamed everywhere.
Thanks.
Please let me know is there a way to restrict a file for set of users.
in production server we are doing dvelopement, if we rename the
Project Area , Stream , Componenet and Reepository workspace does it affect on the exiting code.
Regards,
Sriramak
#######################
Folder level restrictions are not available in 3.x this is planned for 4.x. Restrictions/permissions can be done on component, stream.
I am not sure what the audit issue is due to missing context, but I believe if a component is renamed it is renamed everywhere.
Please let me know is there a way to restrict a file for set of users.
in production server we are doing dvelopement, if we rename the
Project Area , Stream , Componenet and Reepository workspace does it affect on the exiting code.
Regards,
Sriramak
#######################
Thanks for the info..
Please let me know the inputs for below topics...
HOw are we going to restrict the users in folder level.
due to audit issue we are planning ro Rename the Project area, Component, stream and Repository workspace in the production evnrionmnet..
Folder level restrictions are not available in 3.x this is planned for 4.x. Restrictions/permissions can be done on component, stream.
I am not sure what the audit issue is due to missing context, but I believe if a component is renamed it is renamed everywhere.
Thanks.
Please let me know is there a way to restrict a file for set of users.
in production server we are doing dvelopement, if we rename the
Project Area , Stream , Componenet and Reepository workspace does it affect on the exiting code.
Regards,
Sriramak
#######################
Hi Sriramak,
In 3.x you can restrict access to files in SCM on stream and component level based on ownership of the stream and component. You can restrict visibility to
the members of the owner of the stream/component. If you want to restrict file access you have to place the file in a restricted component/stream.