On Wed, 22 Oct 2014, Thierry Carrez wrote:
So while I think periodic jobs are a good way to increase corner case testing coverage, I am skeptical of our collective ability to have the discipline necessary for them not to become a pain. We'll need a strict process around them: identified groups of people signed up to act on failure, and failure stats so that we can remove jobs that don't get enough attention.
It's a bummer that we often find ourselves turning to processes to make up for a lack of discipline. If that's how it has to be how about we make sure the pain if easy to feel. So, for example, if there are periodic jobs on master and they've just failed for a project, how about just close the gate for that project until the failure identified by the periodic job is fixed? -- Chris Dent tw:@anticdent freenode:cdent https://tank.peermore.com/tanks/cdent _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
