[Openstack] [OpenStack-Infra] [Zuul] Understanding dequeue-on-new-patchset

James E. Blair corvus at inaugust.com
Thu Aug 21 22:11:13 UTC 2014

"trinath.somanchi at freescale.com" <trinath.somanchi at freescale.com> writes:

> Hi-
> I configured Zuul with paramater, 'dequeue-on-new-patchset: true'.
> With this, for a change, if multiple patchsets are in queue, only the latest must be taken and rest all to be ignored.
> But I noticed that every patchset is going to zuul-merger to Geraman and to Jenkins finally.
> Is there any configuration in Zuul I need to take care of.
> Kindly help me in this regard.

If a change is in a pipeline with, say, patchset 1, and then someone
uploads patchset 2, the first should be removed from the pipeline and
then patchset 2 enqueued.

Strictly speaking, that will mean that every patchset will go through
the merger and Jenkins.  But if testing for a patchset is in progress
when a new patchset is uploaded, the tests will abort.

If that's not what's happening, can you please provide your layout file
along with debug level log messages from startup as well as a time when
a change was erroneously not dequeued?



More information about the Openstack mailing list