Open Stack

Hello jlvillal, thiagop
Hello krtaylor

In Cinder, 3rd party CIs are asked to set their recheck keyword to "run XXX CI" (also Note it in the CI's Wiki), so that the infra CI will not get kicked.
Maybe we can decide one for our Ironic, too, on the next Wednesday.

Best regards,
Watanabe.isao


> -----Original Message-----
> From: Villalovos, John L [mailto:john.l.villalovos at intel.com]
> Sent: Wednesday, June 29, 2016 9:24 AM
> To: OpenStack Development Mailing List (not for usage questions)
> Cc: ufcg-oneview-ci at lsd.ufcg.edu.br
> Subject: Re: [openstack-dev] [ironic] UFCG OneView CI comments missing recheck
> command
> 
> 
> 
> > -----Original Message-----
> > From: Thiago Paiva [mailto:thiagop at lsd.ufcg.edu.br]
> > Sent: Tuesday, June 28, 2016 17:00
> > To: OpenStack Development Mailing List (not for usage questions)
> > Cc: ufcg-oneview-ci at lsd.ufcg.edu.br
> > Subject: Re: [openstack-dev] [ironic] UFCG OneView CI comments missing
> > recheck command
> >
> > Hi Jay,
> >
> > Sorry about that. The comment should be "recheck oneview" to test again.
> > I'll patch the failure message with instructions, thanks for the warning.
> 
> I'm not sure "recheck oneview" is a good command because it will kick off the
> master recheck. I would suggest something that will not trigger the normal jobs
> to recheck.
> 
> "retest oneview"??  Hopefully there is some standard for 3rd Party CI to use.
> 
> And yes, please do put in the message the command to do a job recheck.
> 
> John
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev