[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
rin_ne closed JENKINS-18338 as Not A Defect Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Seem already fixed. Documented on both Gerrit and Gerrit Trigger Default option is changed from --verified to --label --label Verified works fine on Gerrit 2.8.2 So close. Change By: rin_ne (09/Apr/14 8:53 AM) Status: Resolved Closed 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Ok. I did some testing. There are 2 issues. 1. You need to add explicitly new access right (All Projects: Global Capabilities-Administrate Server-Stream Events) for the Non-Interactive Users group. This was not necessary with the previous Gerrit releases, so after the upgrading to 2.7 - it is missing. The symptom of the missing access right is: gerrit.stream-events 0ms 2ms not-admin In the gerrit sshd_log file. I believe there should be some note in the Gerrit's and Gerrit Trigger Plugin about the fact. 2. Gerrit 2.7 is not backward compatible or there was a bug introduced in the version: The problem: $ ssh gerrit gerrit review --verified +1 9990133e3df3b777a1fc5ba8d8d59677bdc65856 fatal: "--verified" is not a valid option It works perfeclty fine with the Gerrit 2.6. I didn't find any sensible error message, so it is not easy to find the root cause. Would be nice if someone confirms it. I will ask Gerrit's community if it is a feature or a bug.. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed edited a comment on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. 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. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed edited a comment on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. 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 in the logs (Jenkins + Gerrit), 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. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Linked Gerrit's thread: https://code.google.com/p/gerrit/issues/detail?can=2start=0num=100q=colspec=ID%20Type%20Stars%20Milestone%20Status%20Priority%20Owner%20Summarygroupby=sort=id=1963 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
rin_ne commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. 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). Seems it is already noted in Gerrit 2.7 document. http://gerrit-documentation.googlecode.com/svn/Documentation/2.7/cmd-stream-events.html#_access $ 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 in the logs (Jenkins + Gerrit), so it is not easy to find the problem. This might be a bug or new feature. BTW, did you try to use --label option instead --verified option? http://gerrit-documentation.googlecode.com/svn/Documentation/2.7/cmd-review.html#_synopsis If works fine with --label option, may be able to customize the above command using custom command feature in management page. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. @rin_ne - I think that the custom command feature in management page would be the best idea, it allows to integrate the plugin even with customized Gerrit workflows which is different that the default one (all the labels and values (+1,+2,+3..) are customizable in Gerrit). However.. "ssh gerrit gerrit review --label Verified=1" -does not work too with 2.7, with 2.6 it works like expected. "ssh gerritblr gerrit review --label Code-Review=2" -works fine on both, 2.6 and 2.7 Seems like a bug in Gerrit. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed edited a comment on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. @rin_ne - I think that the custom command feature in management page would be the best idea, it allows to integrate the plugin even with modified Gerrit workflows which are very different that the default one (all the labels and values (+1,+2,+3..) are customizable in Gerrit). However.. "ssh gerrit gerrit review --label Verified=1" -does not work too with 2.7, with 2.6 it works like expected. "ssh gerritblr gerrit review --label Code-Review=2" -works fine on both, 2.6 and 2.7 Seems like a bug in Gerrit. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Gavin Swanson commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. I upgraded from gerrit 2.5 to gerrit 2.7 via 2.6 (was only running 2.6 for a day or so). The only change I've made to the configuration of the way Gerrit and Jenkins interact is to add the Stream Events permission. Once that was added everything started working again. I have not had to make any changes to the Gerrit Trigger lines that actually mark things as verified, etc. Although this permission is documented it would have been nice to see something in the Release notes that called out this sort of interaction as requiring it. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Gavin Swanson resolved JENKINS-18338 as Not A Defect Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. I believe that although this is a communication/documentation issue it is in fact not a bug. The main problem here is the addition of the new permission requirements in gerrit which makes this not a Jenkins bug. The secondary problem which may require it's own bug (on Gerrit or Gerrit Trigger) is the potential issue with the --verified flag no longer working. Change By: Gavin Swanson (25/Jul/13 8:05 PM) Status: Open Resolved Resolution: NotADefect 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Recently there was a new Gerrit Trigger plugin released: https://github.com/jenkinsci/gerrit-trigger-plugin/compare/gerrit-trigger-2.10.0...gerrit-trigger-2.10.1 rinrinne Add provider attribute into gerrit events 151724c rinrinne Add trigger parameters using provider attribute in extended event I think there is a chance that it fixes integration with Gerrit 2.7 - need to be tested. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
rin_ne commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Could you add the user used by this plugin to "Non-Interactive Users" group in gerrit 2.7? 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Before Gerrit 2.7, adding the jenkins user to "Non-Interactive Users" group was necessary too, so in the case when you upgrade Gerrit from 2.5 or 2.6 to 2.7 - the user should be already assigned to the proper group and no any additional step is needed. This is exactly my case - the user is already assigned to the "Non-Interactive Users" group. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
rin_ne commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Hmm...works fine on my below environments. Production Gerrit: 2.7-rc1 Jenkins: 1.523 Gerrit Trigger: 2.10.1 Jenkins start command: java -jar jenkins.war From gerrit-trigger repository Gerrit: 2.7-rc1 Jenkins: 1.424 Gerrit Trigger: 2.10.0 Jenkins start command: mvn hpi:run 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
rin_ne commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Seems operation issue. Did you face this issue after gerrit connection is established? or connection has never been established after upgrading? If never established, you can try the below steps: 1. Visit "Gerrit Trigger" page in Jenkins. 2. Push "Stop" in the bottom. 3. Push "Start" in the bottom. 4. Reload page. And you should check gerrit log. (especially sshd_log). 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Gavin Swanson commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. I would like to see a fix for this as well. Kills the Auto part of Automation. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
rin_ne commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. New Stream Events global capability has been added since gerrit 2.7. See "New FeaturesGeneral" section in http://gerrit-documentation.googlecode.com/svn/ReleaseNotes/ReleaseNotes-2.7.html 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Will test this soon. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
ecv commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. I have the same issue. I need also a fix for it. Or a workaround (I know, perhaps downgrading if needed). Greetings Eric 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
rin_ne commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. You should test on console using the below command: $ ssh -p GERRITPORT -i /path/to/privatekeyfile USERNAME@GERRITHOST gerrit stream-events 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
James Nguyen commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Is there going to be a fix for this? I'd hate to have to rollback since I moved up to 2.7-rc2 to fix a bug. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed created JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Issue Type: Bug Affects Versions: current Assignee: rsandell Components: gerrit-trigger Created: 13/Jun/13 2:17 PM Description: After upgrading Gerrit server from 2.5 to 2.7-rc01 I see the following message: "The connection to Gerrit is down! Check your settings and the Gerrit server. Since the connection is down, Jenkins cannot determine the Gerrit version. So all Gerrit features have been enabled." Jenkins was rebooted few times. Triggering mechanism for new changes in Gerrit does not work anymore. Same setup was working fine with the Gerrit 2.5-rc2 release Environment: Gerrit 2.7-rc01 Jenkins ver. 1.517 2.10.0 Project: Jenkins Priority: Blocker Reporter: Piotr Szwed 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Triggering builds manually with the plugin works fine. Same with the "search" functionality. 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. Hi everyone. I need this bug/feature so much that I'm willing to pay 100.00 bucks for it. This offer is registered at FreedomSponsors (http://www.freedomsponsors.org/core/issue/276/gerrit-27-rc01-the-connection-to-gerrit-is-down-check-your-settings-and-the-gerrit-server). Once you solve it (according to the acceptance criteria described there), just create a FreedomSponsors account and mark it as resolved (oh, you'll need a Paypal account too) I'll then check it out and will gladly pay up! If anyone else would like to throw in a few bucks to elevate the priority on this issue, you should check out FreedomSponsors! 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed commented on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. I've just performed partial rollback to gerrti 2.6-rc4 and plugin seems to work fine. The problem must be Gerrit 2.7-rc1 specific 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-18338) Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server.
Piotr Szwed edited a comment on JENKINS-18338 Gerrit 2.7-rc01 - The connection to Gerrit is down! Check your settings and the Gerrit server. I've just performed partial rollback to gerrti 2.6-rc4 and plugin seems to work fine. The problem must be Gerrit 2.7-rc1 or 2.6 specific 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 jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
