Having a version that doesn't require an SCM is unlikely to happen in the
foreseeable future. We require an SCM to grab the full files so we can even
build the diffs. There's way too much that would have to be changed and
worked around if we were to remove this requirement.
I would much rather som
OK,
I am beginning to see Dan's point of view.
think I am going to put off the idea of getting RB to work with
ClearCase at this point.
I have discovered a reference to "/vobs" substring as part of the file
path in postreview.
# Removing anything before the last /vobs
# because it may be repe
Indeed.. Shame IBM isn't using Review Board (at least, I don't know if they
are). Maybe they could give us a license or some code or something.
Little by little, I'm setting up some build/test VMs, and I'm hoping to get
to a point where we can have better post-review and Review Board tests
against
I don't know how similarly people use Clearcase, but I am fairly
certain that the way my organization uses it is very non-standard. The
typical review scenario would be to review modified code in a view,
not checked in code.
Fitting Clearcase's model into Reviewboard is a bit of square in round
ho
At least for ClearCase, most places have a standard naming convention
for their views and/or config specs.
Either way all it takes is for the client to prompt for and pass two
view tags (strings) or config specs (small ascii files) in order for
the web server to start the "before" and "after" vie
Thilo-Alexander Ginkel wrote:
On Friday 15 January 2010 23:20:32 Sassan wrote:
I am also thinking it might be a good idea to add a repository
independent base functionality to the post-review script where it is
handed the root directory of two source trees, before and after the
change and it
On Friday 15 January 2010 23:20:32 Sassan wrote:
> I am also thinking it might be a good idea to add a repository
> independent base functionality to the post-review script where it is
> handed the root directory of two source trees, before and after the
> change and it will then just compare the f
I am also thinking it might be a good idea to add a repository
independent base functionality to the post-review script where it is
handed the root directory of two source trees, before and after the
change and it will then just compare the files and post a review.
This way anyone with any source
I am happy to try to catch up with python scripting add that
functionality and possibly more to it.
I would like some instructions on how and where to get the source out
of git and any special tools I will need for development.
Thanks,
Sassan
On Jan 15, 3:35 pm, Christian Hammond wrote:
> I wo
I would love a patch to move that functionality out into a .reviewboardrc. I
haven't done it myself due to lack of a Clearcase server to test with
(though if anybody wants to donate a license, we can get some automated
tests for stuff going :).
Christian
--
Christian Hammond - chip...@chipx86.co
Hi Sassan,
The latest docs have some instructions on how to use post-review with
Clearcase. In fact, it's the only way to post a review with Clearcase.
http://www.reviewboard.org/docs/manual/dev/users/tools/post-review/
I wrote it using some unix-ish examples, but I actually tested the
instructi
Does anyone know what is and is not currently supported for ClearCase
as an SCM tool on Windows?
For example I see instructions for posting commited code reviews using
post-review.exe under ClearCase section in
http://www.reviewboard.org/docs/manual/1.0/users/tools/post-review/
Does the "Todo" m
12 matches
Mail list logo