Duplicate Source control items in a Project Area
Dear Experts,
We have a environment where there are about 13 streams involving n number of components. The developers of each component are mostly independent of each others work. Considering we have an File A in Component B of Stream X, a developer without being aware of this, adds another File A in Component C of Stream Y within a project area. Now, we loose track of correct file which also creates a duplicate item. Is there any way we can prevent such a scenario where a validation is thrown when a user tries to add a file that already exists in the project area?
Regards,
Sunita
We have a environment where there are about 13 streams involving n number of components. The developers of each component are mostly independent of each others work. Considering we have an File A in Component B of Stream X, a developer without being aware of this, adds another File A in Component C of Stream Y within a project area. Now, we loose track of correct file which also creates a duplicate item. Is there any way we can prevent such a scenario where a validation is thrown when a user tries to add a file that already exists in the project area?
Regards,
Sunita
3 answers
Hi Sunita,
there is nothing to prevent this. There are options you can set on the server to prevent creating components with the same name but not for files.
I actually doubt this is a problem at all for the following reasons.
1. The files belong to (eclipse) projects that reside in the component So adding the same file with the same name to different projects does not create any naming conflict. Adding them to different components less so.
If due to delivery two developers detect they have created a file with the same name in exactly the same place in a project in the same component, the conflict will be displayed and the user trying to deliver later can rename his file. The same if these conflicts occur when accepting changes across different streams.
If that is not the case for you I don't understand the use case good enough. so what issues have you seen that would require such a rule?
there is nothing to prevent this. There are options you can set on the server to prevent creating components with the same name but not for files.
I actually doubt this is a problem at all for the following reasons.
1. The files belong to (eclipse) projects that reside in the component So adding the same file with the same name to different projects does not create any naming conflict. Adding them to different components less so.
If due to delivery two developers detect they have created a file with the same name in exactly the same place in a project in the same component, the conflict will be displayed and the user trying to deliver later can rename his file. The same if these conflicts occur when accepting changes across different streams.
If that is not the case for you I don't understand the use case good enough. so what issues have you seen that would require such a rule?
A warning for this has been requested in work item 83364. This is what
ClearCase would call "evil twin detection". Please feel free to add a
comment to that work item indicating your interest/support.
Cheers,
Geoff
On 11/16/2011 6:23 AM, sdinakar wrote:
ClearCase would call "evil twin detection". Please feel free to add a
comment to that work item indicating your interest/support.
Cheers,
Geoff
On 11/16/2011 6:23 AM, sdinakar wrote:
Dear Experts,
We have a environment where there are about 13 streams involving n
number of components. The developers of each component are mostly
independent of each others work. Considering we have an File A in
Component B of Stream X, a developer without being aware of this,
adds another File A in Component C of Stream Y within a project area.
Now, we loose track of correct file which also creates a duplicate
item. Is there any way we can prevent such a scenario where a
validation is thrown when a user tries to add a file that already
exists in the project area?
Regards,
Sunita
Thank you for the reply Geoff and Ralph. I will follow up on the work item.
But Evil Twin refers to two or more items having the same file name on the same directory right?
But in our case, we would not like to allow the same file name across streams but in the same project area.
Regards,
Sunita
But Evil Twin refers to two or more items having the same file name on the same directory right?
But in our case, we would not like to allow the same file name across streams but in the same project area.
Regards,
Sunita
A warning for this has been requested in work item 83364. This is what
ClearCase would call "evil twin detection". Please feel free to add a
comment to that work item indicating your interest/support.
Cheers,
Geoff
On 11/16/2011 6:23 AM, sdinakar wrote:
Dear Experts,
We have a environment where there are about 13 streams involving n
number of components. The developers of each component are mostly
independent of each others work. Considering we have an File A in
Component B of Stream X, a developer without being aware of this,
adds another File A in Component C of Stream Y within a project area.
Now, we loose track of correct file which also creates a duplicate
item. Is there any way we can prevent such a scenario where a
validation is thrown when a user tries to add a file that already
exists in the project area?
Regards,
Sunita