Maybe one more thing - The adding of custom repository shows the
"Environment can only contain strings" error. I know this is not a way that
will help me, but still it seems like a bug worth solving to me...
Dne středa 24. června 2020 10:40:53 UTC+2 kort...@email.cz napsal(a):
>
> I think we are
I think we are on the end of the road. The last statement from GitLab guys:
"
We're not planning to work on this.
What about the possibility #4 - fetch the git repository?
"
I don't suppose possibility #4 will work for you. So there goes using a
convenient way of code review :-/
There is still
This finally sounds like we are getting somewhere :-) Thank you very much
for the investigation.
First reaction from the Gitlab side is:
"
Well, it seems that they are using API token for non-API urls. That's not
allowed (since one ot the many security updates). Therefore it can work
only with
The GitLab support would like to see which commands are sent from your
side, so they can identify what is wrong.
Dne sobota 20. června 2020 5:13:40 UTC+2 Christian Hammond napsal(a):
>
> All the GitLab API commands? No, we don't log that I'm afraid. What do you
> want to see out of it?
>
> Chris
Is it possible to see in Review Board dump of all executed API commands?
Dne středa 17. června 2020 12:45:13 UTC+2 kort...@email.cz napsal(a):
>
> I finally got to someone competent on the GitLab side, so maybe we will
> get somewhere... His first idea is that the credentials management is
> som
I finally got to someone competent on the GitLab side, so maybe we will get
somewhere... His first idea is that the credentials management is somehow
incompatible between review board and our GitLab. He is investigating now.
Meanwhile we succeeded in using the RBTools to some extent. We don't ha
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 napsal(a
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 as
Hi Christian,
Unfortunately I am still struggling.
The gitlab support directed me to check this:
https://www.reviewboard.org/docs/manual/1.5/admin/management/repositories/#determining-repository-information
This sounded like exactly my problem, for I see the branches, but cannot
access a sing
Hi Christian,
Thanks, I have contacted our GitLab support and hopefully it will have a
good ending.
The colleague testing the RBTools was using this guide
https://www.reviewboard.org/docs/rbtools/1.0/workflows/git/#rbtools-workflow-git
But ended with
CRITICAL: [Error 267] The directory name is
Update:
When we tested it with a "public" repository on our gitlab server, it
works. But our repositories needs to be private.
So it seems the problem is somewhere in the recognition of the reviewboard
as a valid user, even though I filled in all the tokens and keys and user
credentials...
Ri
Hi Christian,
Thanks for the ideas, my admin managed to update reviewboard to 3.0.17, but
no luck.
I found out I am missing the SSH settings, so I created a new one and added
the public part to our gitlab repository, but that was not it either...
I am running out of ideas... is there some infor
Hi again,
There is another problem... I tried to create a review request from the
branches and commits I see and I get
"HTTP 500 INTERNAL SERVER ERROR"
What is wrong? Any idea? Isn't the problem, that our reviewboard is running
on https and port number 444?
Log for this error:
ERROR
- root
Hi Christian,
We are trying to make the RBTools work in the meantime, but is there any
progress in "looking into it" ? :-)
If you say you fixed it, couldn't be the problem, that we use version
3.0.12? We installed the RB on windows using the Bitnami installer and it
has already version 3.0.17
Hello,
I managed to connect to my Gitlab repository and when I am creating new
review I see the repository allright, I even see the branches and commits
on them, but the problem is I don't see all the branches.
I only see exactly 20 of them. I am not sure if they are the newest ones or
by which
15 matches
Mail list logo
