Community
Participate
Working Groups
Our hudson build job recommenders.gerrit on sandbox gets called on each commit but does not report back the results to gerrit anymore. I'm not aware of any changes we may have made. Any idea what may go wrong?
The Gerrit plugin fell over and the sandbox had to be restarted. Are you still seeing this? -M.
it's still not reporting to gerrit. change: https://git.eclipse.org/r/#/c/6201/ build: https://hudson.eclipse.org/sandbox/job/recommenders.gerrit/38/console
I'm also seeing this for Mylyn build jobs.
also Hudson doesn't vote anymore for jgit and egit
Well from the Gerrit plugin admin panel the 'test connection' button returns 'Success'. However I noticed this on the main manage hudson page: The Gerrit-trigger send commands queue contains 257 items! Something might be stuck, or your system can't process the commands fast enough. Try to increase the number of sending worker threads on the Gerrit configuration page. I've turned up the number of threads, and restarted the plugin to see if it clears out the queue. After 20 minutes it's reporting only 25 items in the queue. I don't see anything in Hudsons log or the Gerrit error log that indicates a specific error. I can use the Hudson users Gerrit credentials to login to Gerrit via the command line. The only other recent change I can think of, was granting the 'manual' trigger permission to Matthias. -M.
I started getting comments about completed builds on a number of Mylyn reviews but not for new builds that were triggered.
The queue had filled to 83 items and the plugin was failing to restart, so I restarted the entire sandbox instance. -M.
The issue is back. Gerrit trigger gets executed but does not report back.
*** Bug 382569 has been marked as a duplicate of this bug. ***
The manage Hudson page was reporting 226 items in the queue. I checked the connection(it reported success) but the queue didn't seem to be moving. Just before I restarted the sandbox I noted that there seemed to be a 'stuck' Hudson job from the 29th of May. The queue is presently 'empty'. -M
One hour ago, Hudson reported to start the build for a second change-set but didn't report back the build's result. I guess Gerrit Trigger is taking holidays again?
I don't see any errors in the logs, but I restarted the sandbox just in case. -M.
this works for jgit and egit, I think we can close this