Excerpts from Andreas Jaeger's message of 2017-02-01 15:37:15 +0100: > On 2017-02-01 15:27, Doug Hellmann wrote: > > [...] > > Another option was to have the release bot continually propose > > updates to the same patch, like we do with the global requirements > > sync job. On any given day, that's going to cause a bunch of resets > > on the patch, until we merge it. That will be particularly annoying > > if we release something while the patch is in the gate queue ready > > to be merged, but even in the check queue it will "waste" test nodes > > on each reset. > > Note that the proposal jobs can check whether a job is in the gate queue > and do not propose anything at that time, see > http://git.openstack.org/cgit/openstack-infra/project-config/tree/jenkins/scripts/common.sh#n69 > - the check_already_approved function. > > Whether you want to use it in this case, is up to you. For these kind of > jobs that run often, it might be a good idea, > > Andreas
Oh, that's definitely a good option to have. Thanks for pointing that out! Doug __________________________________________________________________________ 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
