Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jgit-dev] Hudson down?

On Fri, Jul 10, 2015 at 11:58 AM, Alex Blewitt <alex.blewitt@xxxxxxxxx> wrote:

On 10 Jul 2015, at 19:08, Dave Borowitz <dborowitz@xxxxxxxxxx> wrote:

On Thu, Jul 9, 2015 at 11:57 PM, Alex Blewitt <alex.blewitt@xxxxxxxxx> wrote:
What if the gerrit page had a "retrigger" that could send a repeat of the event to the ssh stream that included the change?

Which event? There are potentially dozens of events represented on a given change screen; are you proposing buttons next to each patch set/reviewer/inline comment/message?

However there's typically only one or two that are picked up to trigger builds:

The default one is "patchset created" so I'd suggest this is the right one to resend down the stream to re-trigger downstream builds. 

People are always asking us "when are you going to support stream-events on", and stuff like this is why my answer is usually "are you sure you want that? 'cause it kinda sucks."

OTOH this thread was kicked off because of a user of stream-events and has no bearing on whether it would be useful for

I'm just saying that stream-events is tricky and error-prone for _anybody_ and that's why I generally steer people in the direction of polling ;)

A real reliable many-to-many pubsub service with redelivery, etc. would be nifty, but stream-events is not that.

That way you wouldn't have to rely on where the server is located and you could also retrigger failed jobs where there was a transient problem in building which was unrelated to your change. Would be better than having to amend the commit message or doing a rebase, which are the two ways you can manually do this at the moment. 


Sent from my iPhat 6

On 9 Jul 2015, at 22:45, Matthias Sohn <matthias.sohn@xxxxxxxxx> wrote:

On Thu, Jul 9, 2015 at 6:56 PM, Dave Borowitz <dborowitz@xxxxxxxxxx> wrote:
I have a series I pushed yesterday that hasn't gotten any attention from Hudson:

Any ideas why?

sometimes the ssh connection used by the gerrit-trigger plugin stops working.
Hudson admins can restart it by clicking a button under "Manage Hudson > Gerrit Trigger".

Newer versions of the gerrit-trigger plugin available for Jenkins have a
watchdog thread which auto-restarts the connection in case there are no stream events
for a configurable time period.

The latest gerrit-trigger version available for Jenkins is 2.14.0
the latest one available for Hudson is 2.5.3-h-2
on the JGit Hudson 2.5.3-h-1 is installed.

I filed
to request a modern gerrit-trigger version for Hudson

Alternatively we could raise more voices for Jenkins on

You can manually (re-)trigger a build for voting jobs here
enter a Gerrit query to find your change, select the patchset you want to build and click
"Trigger Selected".

jgit-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top