|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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/groups/opt_out.
Ok. I did some testing. There are 2 issues.
1. You need to add explicitly a new access right (All Projects: Global Capabilities->Administrate Server->Stream Events) to the Non-Interactive Users group. This is something new and it was not necessary for the previous Gerrit releases (<2.7).
The symptom of the missing access right is: "gerrit.stream-events 0ms 2ms not-admin" - in the Gerrit's sshd_log file.
I believe there should be added some note about it in the documentation (of both: Gerrit and Gerrit Trigger Plugin)
2. Gerrit 2.7 is not backward compatible or there was a bug introduced in the 2.7 version:
The problem:
$ ssh gerrit gerrit review --verified +1 9990133e3df3b777a1fc5ba8d8d59677bdc65856
fatal: "--verified" is not a valid option
It works perfectly fine with the Gerrit 2.6. I didn't find any sensible error message, so it is not easy to find the problem.
I will ask Gerrit's community if it is a feature or a bug..![]()
, there is a possibility to use different parameter (--label) instead of --verified, but We should know first what is the proposed solution by Gerrit.