Did you upgrade ReviewBoard? To what version did you upgrade?
I'm struggling with a GitLab problem right now, and certainly got past what
you describe when using ReviewBoard 3.0.14.
Eric
On Monday, May 13, 2019 at 12:51:03 AM UTC-7, Akshay Agarwal wrote:
>
> Can someone help?
>
> On Friday,
Can someone help?
On Friday, May 10, 2019 at 4:28:34 PM UTC+5:30, Akshay Agarwal wrote:
>
> We have decided to proceed by upgrading the Review Board. The error I am
> getting while setting up the Gitlab repo is as follows:
>
> Unexpected error when linking the account: Could not determine the
Also, can the Review Board be compatible with an older version of Gitlab?
On Monday, May 6, 2019 at 9:22:58 AM UTC+5:30, Akshay Agarwal wrote:
>
> Just how Gitlab has the option of communicating with Bitbucket, is the
> same possible with cgit or gitweb?
>
> On Saturday, May 4, 2019 at 2:00:09
Just how Gitlab has the option of communicating with Bitbucket, is the same
possible with cgit or gitweb?
On Saturday, May 4, 2019 at 2:00:09 AM UTC+5:30, Christian Hammond wrote:
>
> Cgit and Gitweb are alternatives to using a service like GitLab. You can
> use those with a self-hosted, raw
Cgit and Gitweb are alternatives to using a service like GitLab. You can
use those with a self-hosted, raw git repository, which we discussed at
length in the other thread. But you have to understand, your choices are
limited to the options we are able to support with the version of Review
Board
So Review Board 2.0.21 is not compatible with Gitlab even after using Cgit
or Gitweb. You also said it will not work with Bitbucket either. You need
to understand that Review Board is being used for a corporate product here
and it is not that easy to just upgrade as there are many dependencies
2.0.21 is 4 years old, and GitLab no longer fully supports the version of
the API that Review Board 2.0.21 was compatible with. We also don't provide
any support for Review Board 2.0.x, so you'll need to upgrade to the 3.0.x
series if you want to use GitLab.
Christian
On Fri, May 3, 2019 at 1:05
Since there is an option to add the Gilab repo in version 2.0.21, there
must be another way to communicate with Gitlab right?
On Friday, May 3, 2019 at 1:11:20 PM UTC+5:30, Akshay Agarwal wrote:
>
> Could I use Cgit or Gitweb between gitlab and reviewboard?
>
> On Fri, 3 May 2019 at 12:36 PM
Could I use Cgit or Gitweb between gitlab and reviewboard?
On Fri, 3 May 2019 at 12:36 PM Christian Hammond
wrote:
> Ah, that explains it. 2.0.x is now a few generations behind and no longer
> supported by us in any form. The 2.5.x series followed, and 3.0.x is the
> current and supported
Ah, that explains it. 2.0.x is now a few generations behind and no longer
supported by us in any form. The 2.5.x series followed, and 3.0.x is the
current and supported release. You'll need 3.0.x for GitLab support, as
it's the only generation that supports the modern GitLab API.
Christian
On
Version 2.0.21
On Fri, 3 May 2019 at 12:28 PM Christian Hammond
wrote:
> What version of Review Board are you running?
>
> Christian
>
> On Thu, May 2, 2019 at 10:06 PM Akshay Agarwal
> wrote:
>
>> While the Review Board documentation shows an option to add an api token
>> for Gitlab, there is
What version of Review Board are you running?
Christian
On Thu, May 2, 2019 at 10:06 PM Akshay Agarwal wrote:
> While the Review Board documentation shows an option to add an api token
> for Gitlab, there is no such option to do so in the Review Board. It only
> asks url, username and the
While the Review Board documentation shows an option to add an api token
for Gitlab, there is no such option to do so in the Review Board. It only
asks url, username and the password. The error being shown is "error when
linking the account: HTTP Error 410" The same has been shown in the file
13 matches
Mail list logo
