[Starlingx-discuss] upstream -infra queue setup might need tweaking to handle cross-project dependencies

Scott Little scott.little at windriver.com
Wed Jun 27 19:31:59 UTC 2018

Agreed, I don't think we can function without it.

Is there a way to get a notification sent to reviewers of the blocking 
review, the one that is depended on but is not recieved it's CR+2, W+1, 
that this review needs urgent attention?

If the depended on review is failed or abandoned, can the blocked review 
by automatically dequeued?  Demoted to W0?  Ideally with a notification?


On 18-06-27 03:12 PM, Dean Troyer wrote:
> On Wed, Jun 27, 2018 at 1:43 PM, Chris Friesen
> <chris.friesen at windriver.com> wrote:
>> The automated way to handle this is to have all the potentially
>> interdependent projects share a queue by specifying a common queue name.
>> The example given was the "integrated" queue for nova and friends, as
>> specified at
>> https://git.openstack.org/cgit/openstack-infra/project-config/tree/zuul.d/projects.yaml#n108
> Dang, I forgot this bit when setting up the jobs, so something like
> this? https://review.openstack.org/578532
>> This does potentially introduce merge delays since it will serialize merges
>> across all the projects that share a queue, but for tightly-coupled projects
>> it might make sense.
> It think totally makes sense here...
> dt

More information about the Starlingx-discuss mailing list