Hi, Dan,

CCRC is Java standalone GUI application to work with views based on
Eclipse platform. The installation doesn't contain cleartool. It's
completely different interface. Something about it locates here:

https://publib.boulder.ibm.com/infocenter/cchelp/v7r1m0/index.jsp?topic=/com.ibm.rational.clearcase.cc_ms_install.doc/topics/t_install_ccrc_standalone.htm

http://www.samecs.com/how_do_i/ClearCase%20Remote%20Client%20and%20web/ClearCase%20remote%20client%20and%20ClearCase%20web%20how%20do%20I.htm

CCRC doesn't require additional server. In our company the only
ClearCase server is used by developer. We use snapshot views. I've
discussed with other developers this topic and found out that CCRC can
be used for views created by cleartool and otherwise. CCRC is
alternative for cleartool.

Now we're testing approach when diff file are generated by
reviewboard, not by post-review.

Michael.
On Aug 18, 5:40 pm, Dan Savilonis <[email protected]> wrote:
> The clearcase support relies on the extended path notation through the
> clearcase filesystem and uses cleartool to query the view. I'd never
> heard of CCRC before, but anything involving Clearcase and the word
> 'remote' can't possibly be a good thing. Do you have any more details
> on how this tools works? Does it ultimately provide an interface to
> cleartool, or is it a completely different, incompatible interface?
>
> Christian: FYI, Clearcase doesn't really have any concept of a remote
> server, akin to svn et al. You have your machine configured on a local
> network with a clearcase server, and you have one or more 'VOBs' that
> are basically repositories. You create a snapshot or dynamic 'view'
> locally that presents the file tree in a directory. You can't really
> just switch to another clearcase server, if there are multiple ones on
> your network. And the only easy way to access different versions of a
> file is through a weird extension to the filesystem where you can
> specify the version as a path (e.g. foo/bar.c@@\main\branch\37)
>
> Dan
>
> On Aug 17, 10:57 am, MiZhKa <[email protected]> wrote:
>
> > Hi, Christian,
>
> > Recently I found out that a lot of developers use CCRC (ClearCase
> > Remote Client) and don't have cleartool. I'm sorry for long delay,
> > because I had limit of time to make Review Board be working with CCRC.
> > The only solution not required high redevelopment was creating page
> > for creating of review requests by repository and activity ID. Diff is
> > generated according to activity ID. Today the solution has been given
> > to developers. Now I'm waiting for first comments. After that, I will
> > post corrections.
>
> > Sincerely yours,
> > Michael,
> > On Aug 13, 10:26 pm, Christian Hammond <[email protected]> wrote:
>
> > > Yes, either upload it through the web UI or use post-review in an SVN
> > > checkout (which is much easier).
>
> > > Christian
>
> > > --
> > > Christian Hammond - [email protected]
> > > Review Board -http://www.review-board.org
> > > VMware, Inc. -http://www.vmware.com
>
> > > On Thu, Aug 13, 2009 at 8:17 AM, MiZhKa <[email protected]> wrote:
>
> > > > Now it works.
>
> > > > How can I send fix? To review.review-board.org?
>
> > > > Thank you,
> > > > On Aug 13, 8:06 am, MiZhKa <[email protected]> wrote:
> > > > > Christian,
>
> > > > > Thank you for your answer! I'll try to fix it. I think fix is easy,
>
> > > > > Michael.
>
> > > > > On 13 авг, 00:34, Christian Hammond <[email protected]> wrote:
>
> > > > > > I think the person who contributed ClearCase support on the server
> > > > expected
> > > > > > that the repository would be locally checked out with the path 
> > > > > > given.
> > > > We'll
> > > > > > certainly take a patch to use cleartool to fix this.
>
> > > > > > We don't have access to ClearCase, so we can't do a lot of testing
> > > > > > ourselves.
>
> > > > > > Christian
>
> > > > > > --
> > > > > > Christian Hammond - [email protected]
> > > > > > Review Board -http://www.review-board.org
> > > > > > VMware, Inc. -http://www.vmware.com
>
> > > > > > On Wed, Aug 12, 2009 at 10:56 AM, MiZhKa <[email protected]> wrote:
>
> > > > > > > Hi,
>
> > > > > > > I wonder how reviewboard fetches file versions from ClearCase. 
> > > > > > > Now I
> > > > > > > have strange error from /api/json/reviewrequests/74/diff/new/:
> > > > > > > {"fields": {"path": ["cat: cat: /usr/cc_storage/unix_STREAM/.../
> > > > > > > myjava.sql@@/main/STREAM/2: No such file or directory\n"]}, 
> > > > > > > "stat":
> > > > > > > "fail", "err": {"msg": "One or more fields had errors", "code": 
> > > > > > > 105}}
>
> > > > > > > It seems that reviewboard (on server side) doesn't use cleartool 
> > > > > > > to
> > > > > > > fetch version of file. This can be seen from 
> > > > > > > scmtools/clearcase.py:
>
> > > > > > > class ClearCaseClient:
> > > > > > >    def __init__(self, path):
> > > > > > >        self.path = path
>
> > > > > > >    def cat_file(self, filename, revision):
> > > > > > >        p = subprocess.Popen(
> > > > > > >            ['cat', filename],
> > > > > > >            stderr=subprocess.PIPE,
> > > > > > >            stdout=subprocess.PIPE,
> > > > > > >            close_fds=(os.name != 'nt')
> > > > > > >        )
> > > > > > >        contents = p.stdout.read()
> > > > > > >        errmsg = p.stderr.read()
> > > > > > >        failure = p.wait()
>
> > > > > > >        if not failure:
> > > > > > >            return contents
>
> > > > > > >        if errmsg.startswith("fatal: Not a valid object name"):
> > > > > > >            raise FileNotFoundError(filename)
> > > > > > >        else:
> > > > > > >            raise SCMError(errmsg)
>
> > > > > > > Is it mistake or my misunderstanding?
>
> > > > > > > Thank you for your help!
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to