Killing obsolete Jenkins builds
sbergman at redhat.com
Thu Nov 19 06:43:57 PST 2015
On 11/19/2015 02:03 PM, Ashod Nakashian wrote:
> On Thu, Nov 19, 2015 at 5:39 AM, Stephan Bergmann <sbergman at redhat.com
> <mailto:sbergman at redhat.com>> wrote:
> By the way, one situation where it is debatable whether all the
> triggered builds are useful is if you push a series of changes to
> gerrit, and Jenkins does builds for each of the changes in the
> series. For me at least, in such a situation it would suffice if
> Jenkins just only did a build for the topmost change.
> Yes, good point. This could be helped by the plugin Samuel mentioned.
> But it'd only work when you know what you're doing and when you are a
> core developer with commit rights (I'd expect patches submitted by the
> community to pass builds/tests before getting reviewed in most cases).
I don't see how pushing a coherent sequence of changes to gerrit is any
different for core and non-core developers. It is just that instead of
having a single, large commit you split it up into meaningful units
(that can depend on previous units).
More information about the LibreOffice