I've noticed that Dell CI has the same problem: it uses "recheck Dell"
causing the whole check pipeline to rerun.
On 06/29/2016 02:23 AM, Villalovos, John L wrote:
-----Original Message-----
From: Thiago Paiva [mailto:thia...@lsd.ufcg.edu.br]
Sent: Tuesday, June 28, 2016 17:00
To: OpenStack Development Mailing List (not for usage questions)
Cc: ufcg-oneview...@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-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
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
