Wireshark mailing list archives

Re: Upcoming Gerrit upgrade


From: Alexis La Goutte <alexis.lagoutte () gmail com>
Date: Wed, 16 Mar 2016 12:41:08 +0100

On Wed, Mar 16, 2016 at 11:02 AM, Graham Bloice <graham.bloice () trihedral com
wrote:



On 16 March 2016 at 09:42, Alexis La Goutte <alexis.lagoutte () gmail com>
wrote:



On Wed, Mar 16, 2016 at 10:25 AM, Graham Bloice <
graham.bloice () trihedral com> wrote:

Gerald,

Slightly related, is there any chance of improving the message
associated with a change as shown in buildbot,  "Gerrit: Patchset(s)
merged" for every change isn't very helpful.

On Petri Dish buildbot ? May be need a update also on buildbot... (there
is "nine" release in dev on Buildbot (with a lot of change...))


I suspect this is the difference between the buildbot GerritChangeSource
handling of the two events, patchset-created and ref-updated as I think the
PD users the former and the main buildbots the latter.

If the main buildbots are using GerritChangeSource it seems that the
change subject isn't available for the ref-updated event.  Which is odd.

I think, master(*) buildbot use only git change (and no directly
GerritChangeSource...)



--
Graham Bloice

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org
?subject=unsubscribe

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe

Current thread: