Wireshark mailing list archives
Gerrit versus Buildbot
From: Chris Kilgour <techie () whiterocker com>
Date: Thu, 20 Mar 2014 11:40:58 -0700
Just had the unpleasant experience of having a patch submitted to gerrit where it sat for nearly one month, just got merged after a code review, then got reverted when buildbot revealed issues. When I have submitted to other gerrit-based projects like OpenOCD, they have an automated build system connected (IIRC it's a standard thing called Jenkins) that provides a +1/-1 to trap build-related issues immediately after submission. Any reason why wireshark doesn't do this? Alternately, is there a way for submitters to access build-bot so we can proof changes prior to merge (or better yet, prior to submission)? Chris Kilgour ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Gerrit versus Buildbot Chris Kilgour (Mar 20)
- Re: Gerrit versus Buildbot Gerald Combs (Mar 20)
- Re: Gerrit versus Buildbot Chris Kilgour (Mar 20)
- Re: Gerrit versus Buildbot Guy Harris (Mar 20)
- Re: Gerrit versus Buildbot Bálint Réczey (Mar 21)
- Re: Gerrit versus Buildbot Bálint Réczey (Mar 26)
- Re: Gerrit versus Buildbot Gerald Combs (Mar 27)
- Re: Gerrit versus Buildbot Chris Kilgour (Mar 20)
- Re: Gerrit versus Buildbot Gerald Combs (Mar 20)