Re: optimal configuration of RB with ClearCase

2010-07-27 Thread Jan Koprowski
Yes Dan. Exactly! I'm 100% agree with You but I don't know how dynamic
view works with UCM :| But there could be a problem with deleted
files. Because there is option to delete it even from ClearCase
history - from VOB. We must do it once and old reviews of this fill
stop working. The bigger problem now is ClearCase doesn't recognize
binary files and try to make diff also for dll, exe, lib and other
files :| which is sad and painful for now. We made a little wrapper
which check is file is not mark as compressed file by ClearCase and
we don't consider this files. But there is a problem sometime. For
example we have *.tcl file marked as compressed_file. Cause was NULL
sign in revision 1 removed in revision 2 but all revisions was marked
as compressed_file. We must delete this object from vob permanentyly
and checkin only latest version one more time to allow this file go
under review.

On Tue, Jul 27, 2010 at 3:23 AM, Dan Savilonis d...@n-cube.org wrote:
 A dynamic view in Clearcase should be able to access any arbitrary
 file or revision associated with the VOB via the MVFS extended path
 notation. So, even if you use a path name that does not exist in your
 working copy due to your current config spec, you should still be able
 to access deletefile@@/branch/5, for example. You should be able to
 test this out directly at the command line. The dynamic view on the
 server is just a vehicle to access the Clearcase database. It doesn't
 matter at all what state it is in. If you think this isn't true, then
 we need to understand why and evaluate other options.

 Dan

 On Jul 22, 4:27 am, Igor xrevol...@gmail.com wrote:
 On Jul 18, 7:25 pm, Jan Koprowski jan.koprow...@gmail.com wrote:

  On Sun, Jul 18, 2010 at 5:39 PM, Igor xrevol...@gmail.com wrote:
   Hi,

   I have same ClearCase setup as described in patch of Jan Koprowski -
  http://reviews.reviewboard.org/r/1505/.
   Correct me if I wrong, in this patch each repository represents
   clearcase view of specific user (repository_url as defined in Jan's
   patch ) under /view/$user_$module_$branch.

  This /view/$user_$module_$branch model looks like misunderstanding.
  View for Review Board is another, different dynamic view distinct from
  others - central view where all branches of all users are present. You
  can get to files on this branches using extended path
  /path/to/file@@/main/branch/version. I don't understand why branches
  in Your model is different views - not standard ClearCase branch.

 OK. I need to fetch original file from central repository. What if
 file was removed from repository on some later stage?
 Do I need to save baseline of original file?

 BTW we use UCM ClearCase

 --
 Want to help the Review Board project? Donate today at 
 http://www.reviewboard.org/donate/
 Happy user? Let us know at http://www.reviewboard.org/users/
 -~--~~~~--~~--~--~---
 To unsubscribe from this group, send email to 
 reviewboard+unsubscr...@googlegroups.com
 For more options, visit this group at 
 http://groups.google.com/group/reviewboard?hl=en



-- 
 Jan Koprowski

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en


Re: optimal configuration of RB with ClearCase

2010-07-18 Thread Jan Koprowski
On Sun, Jul 18, 2010 at 5:39 PM, Igor xrevol...@gmail.com wrote:
 Hi,

 I have same ClearCase setup as described in patch of Jan Koprowski -
 http://reviews.reviewboard.org/r/1505/.
 Correct me if I wrong, in this patch each repository represents
 clearcase view of specific user (repository_url as defined in Jan's
 patch ) under /view/$user_$module_$branch.

This /view/$user_$module_$branch model looks like misunderstanding.
View for Review Board is another, different dynamic view distinct from
others - central view where all branches of all users are present. You
can get to files on this branches using extended path
/path/to/file@@/main/branch/version. I don't understand why branches
in Your model is different views - not standard ClearCase branch.

 It would be a little bit problematic to set up RB when you have
 hundreds of developers and many modules of different branches in
 ClearCase. What would be the optimal RB configuration of ClearCase
 repository in this case? Wouldn't it be more flexible to set up one
 repository under /view/ (for example) and provide a clearcase view for
 each review request and fetch original file according?

 Thanks, Igor.

 --
 Want to help the Review Board project? Donate today at 
 http://www.reviewboard.org/donate/
 Happy user? Let us know at http://www.reviewboard.org/users/
 -~--~~~~--~~--~--~---
 To unsubscribe from this group, send email to 
 reviewboard+unsubscr...@googlegroups.com
 For more options, visit this group at 
 http://groups.google.com/group/reviewboard?hl=en



-- 
 Jan Koprowski

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en