Open Stack

On 06/30/2014 03:04 PM, Kevin Benton wrote:
> Hello all,
> 
> The subject of 3rd party CI voting responses came up in the 3rd-party IRC
> meeting today.[1] We would like to get feedback from the larger dev
> community on what acceptable response times are for third party CI systems.
> 
> As a maintainer of a small CI system that tends to get backed up during
> milestone rush hours, it would be nice if we were allowed up to 12 hours.
> However, as a developer this seems like too long to have to wait for the
> results of a patch.
> 
> One option might be to peg the response time to the main CI response
> assuming that it gets backed up in a similar manner.
> 
> What would be acceptable to the community?
> 
> 1.
> http://eavesdrop.openstack.org/meetings/third_party/2014/third_party.2014-06-30-18.01.html
> 
> 
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 
Thank you for starting this discussion, Kevin.

I look forward to getting some responses from developers. Even if you
don't have a time suggestion, please offer your description of your
workflow and how third party ci responses play a role in that workflow
so we can try to make a good decision here.

Third party ci admins are trying to come up with a standard for testing
response times that the community can accept. If we don't have any input
from developers here, third party ci admins are going to conclude that
developers don't care (I know you do) and pick a time frame that works
for them, which likely won't work for developers.

I look forward to having some options to draw from here. I hope you
consider posting your input.

My thanks,
Anita.