Task #38280

Reactivate Gerrit-Trigger

Added by Christian Trabold 12 months ago. Updated 12 months ago.

Status:Closed Start date:2012-06-22
Priority:Must have Due date:2012-06-22
Assignee:Steffen Gebert % Done:

0%
Category:Infrastructure
Target version:- Estimated time:4.00 hours
Votes: 0

Description

The Gerrit-Trigger is not functioning as normal.

Commits are not recognized since Jun 20, 2012 11:39:15 PM.

Please check if Jenkins can access the machine or if there's a bug in the Gerrit-Trigger-Plugin. Thanks!

gerrit_trigger.png (34.7 kB) Christian Trabold, 2012-06-22 12:45

History

#1
Updated by Christian Trabold 12 months ago

Facts

  • We had no known updates nor restarts on the serverside
  • The gerrit service is running
    # ps aux | grep gerrit
root     17006  0.0  0.0  77040  3400 ?        Ss   11:41   0:00 sshd: typo3-ci-slave-gerrit [priv]
5006     17105  0.1  0.0  77180  1784 ?        S    11:41   0:01 sshd: typo3-ci-slave-gerrit@notty
5006     17133  0.0  0.0  10724  1468 ?        Ss   11:41   0:00 bash -c cd '/home/typo3-ci-slave-gerrit' && java  -jar slave.jar
root     23173  0.0  0.0   7624   936 pts/0    S+   12:03   0:00 grep --color=auto gerrit
  • I get this message from Jenkins (via Gerrit-Plugin):
    The connected Gerrit's version is a snapshot version. Jenkins cannot fully determine what features are available, so all features have been enabled.
  • I can build https://ci.typo3.org/job/typo3-v4-core-gerrit/4547/console so communication from ci.typo3.org to review.typo3.org seems OK.

What I did already

#2
Updated by Christian Trabold 12 months ago

  • File gerrit_trigger.png added
  • Status changed from Accepted to Needs Feedback
  • Assignee changed from Christian Trabold to Steffen Gebert

Connection seems OK:

Did something change on gerrit side?

#3
Updated by Steffen Gebert 12 months ago

I don't know of any changes. Is there anything to do atm?

#4
Updated by Christian Trabold 12 months ago

  • Status changed from Needs Feedback to Closed

I'm very happy to report that Gerrit is triggering Jenkins again.

Maybe restarting the ssh connection did the trick…

Also available in: Atom PDF