Emilien, Thanks for bringing this up!
On Fri, Mar 11, 2016 at 08:00:14AM -0500, Emilien Macchi wrote: > We just broke TripleO CI for a bug we introduced in puppet-nova, so I > thought a reminder would be useful for our group. > > * If Jenkins gives +1 to a patch but some non-voting jobs do not pass, > please look why or at least ask on #puppet-openstack if it's "normal". > * If TripleO or Fuel CI jobs are red, and you have no idea how to debug > them, no problem. Come on IRC and ask some help. > * If you aren't sure about why TripleO & Fuel CI are red and you're about > to +A a patch, please come on IRC and ask guidance. You can find out more about Fuel CI on wiki: https://wiki.openstack.org/wiki/Fuel/CI#CI_for_Puppet_OpenStack And if you notice a failed Fuel CI test on your commit, please come to #fuel-dev, we want to investigate all such failures: https://wiki.openstack.org/wiki/Fuel/CI/Puppet_OpenStack_CI_duty We're still working on setting up everything for this (e.g. Fuel CI doesn't vote yet so we can't setup a gerrit dashboard described on that page), but we do want to catch potential regressions so we will help. -- Dmitry Borodaenko __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
