Hi Ariel,

Unfortunately, we don't otherwise have a way to get data out of GitBlit
today. If they don't expose that feature, we can't get the data needed to
perform code reviews, and other code review tools and services are going to
have the same problem. Git's protocol just doesn't have the kind of
fine-grained access that a code review tool needs, so we depend on the APIs
provided by services like GitBlit.

If you have Review Board running on the same server as GitBlit and can
point Review Board to the local ".git" directory on the filesystem, then
you can do that. Alternatively, you can set up a Git clone that's
constantly in sync, and use that instead.

Christian

-- 
Christian Hammond
President/CEO of Beanbag <https://www.beanbaginc.com/>
Makers of Review Board <https://www.reviewboard.org/>

On Tue, Feb 21, 2017 at 7:30 AM, Ariel Cassan <[email protected]> wrote:

>
> Hi again Christian,
>
> James Morger from Gitblit has replied: "At the moment you are stuck as
> Gitblit doesn't have a way to expose blobs referenced by their ids.  We'd
> have to add a new route handler to accommodate that use-case.  This is not
> difficult, just not presently a feature."
>
> So, can you think of any other way to get the diff feature working on our
> ReviewBoard installation?
> This tool is basic when performing code reviews, so this would actually
> mean we should change ReviewBoard for an alternative tool, with the
> consequent effort.
>
>
> Thanks again for your collaboration.
> Kind regards,
>
> Ariel C.
>
>
> On Thursday, February 16, 2017 at 5:52:59 PM UTC, Ariel Cassan wrote:
>
>>
>> Hi guys,
>>
>> We've started trying out ReviewBoard 2.5.7 as the code review tool for
>> our project, which uses Gitblit as the manager of the git repository,
>> everything on the same server (ReviewBoard + Gitblit + the repo itself)
>> We have configured the repository on ReviewBoard (see attached image) and
>> we have used "rbt post" or "rbt post *hash*" for creating the review
>> requests.
>>
>> However, the "There was an error displaying this diff." is displayed for
>> every file in the request, every time we try it on.
>> We have tried also to create the diff file in local and upload it with
>> "rbt post --diff-filename=xxxx" with the same unsuccessful results.
>>
>> When we take a look at the rejection file in the temp folder, the reason
>> is that either ReviewBoard or GitBlit are trying to use a branch with the
>> name of the raw url's revision!
>> So, the raw URL for Gitblit looks as: http://<IP>:<PORT*>*/raw/<re
>> po_name>.git/<revision>/<filename>.
>> An the error in the rejection file is:
>> <h1>Error</h1><p>Sorry, the repository <repo_name>.git does not have a
>> <strong>65c87f4f676953cb12770a50af3cd405bcb86863</strong> branch!</p>
>>
>> We understand it takes it from the raw URL because the error changes when
>> configuring the raw URL mask as:  http://<IP>:<PORT*>*/raw/<repo_
>> name>.git/<branch>/<filename>.4
>> But of course, it fails anyway as that URL is not returned successfully
>> by Gitblit.
>>
>> Please, can you help us to fix this issue?
>>
>>
>> Thanks in advance.
>> Kind regards,
>>
>> Ariel
>>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "reviewboard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to