Hi Jimmy,
You should be able to simply use Postgres's standard tools for importing
the database onto the new server (or perhaps even just copy all the
underlying files).
Once you have the old version's database on the new server, and you have
the new version of Review Board installed, you'll
We don't talk directly to the repository, or clone it, so that error
probably isn't related to us?
We communicate solely with the GitLab API, and we're using the standard
GitLab API calls. We know that the authentication is working via those
calls, because you'd get an error much earlier. If it's
Hello All,
Would someone be able to provide guidance for importing a copy of the
database from an old instance of ReviewBoard into the newer release of
ReviewBoard?
Thanks
-JG-
P.S. I'm running the latest version that was just released.
--
Supercharge your Review Board with Power Pack:
I just found:
"cloning per https is blocked from the internet, if you want to clone from
internet you need to use ssh"
That seems like the real problem...
sooo... How can I persuade Reviewboard to communicate with GitLab over SSH?
Dne úterý 16. června 2020 15:05:43 UTC+2 kort...@email.cz
Yes, the RBTools seems completely different problem (and we might solve it
yet, we found what we did wrong, need some more testing). We will open
different thread if needed.
The branch limit is also not an issue anymore, we changed the structure, so
now we can reach the branches we need, and
