On 9/21/17, 10:19 PM, "Jeremy Freudberg" <jeremyfreudb...@gmail.com> wrote:
3) Delay spin-up of resource-intensive/long-running CI jobs until after some initial review has been added or time has passed. Authorized contributors, not necessarily synonymous with cores, can override the delay if there's a critical patch which needs to get through the queue quickly. +1. This is done in Go code review process, where CI is run by an explicit Run-TryBot+1 review only after a core developer ascertains that the patch looks okay and most code review comments are addressed. This means no CI resource usage for every change and every single patchset. We could adopt a similar approach so that CI resources aren’t wasted for useless patches. This doesn’t take a whole lot of work for the reviewers than the current review process. https://github.com/golang/go/wiki/GerritAccess#trybot-access-may-start-trybots Thanks, Rajath __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev