For remote access, we need a URL that provides file contents based on blob
sha1. I don't really know anything about gitlab, but we've previously had
pretty good success getting hosting providers to add an API for us when we
need it (access by blob is a pretty trivial thing).
If you can't do that, an in-sync local repo is probably your best bet.
On Tue, Nov 20, 2012 at 12:49 PM, DXM <dxm...@gmail.com> wrote:
> I'm trying to setup ReviewBoard to work with Gitlab repository. Since
> Gitlab has a web front end API, From everything I've read so far, seems the
> most straightforward integration would be to specify a Raw File URL mask in
> the repository setup.
> However, I've run into a bit of a problem. It looks like for <revision>
> placeholder, RB server will pass in file blob's SHA1, but Gitlab API wants
> the client to pass in SHA1 of the commit. So far in all my
> searching/googling I haven't found a way to either modify RB to pass in
> SHA1 of the commit or a different Gitlab HTTP URL that would accept SHA1 of
> the file blob.
> Are you aware of anyone else that successfully integrated Gitlab with
> ReviewBoard? Could I be missing something fundamentally easy?
> Or is my only option to setup a cron job that would periodically update
> local repository on the RB server
> thank you
> -- Dennis
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at