recheck/reverify comment_filter is too loose

Bug #1355480 reported by YAMAMOTO Takashi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Core Infrastructure
Opinion
Undecided
Unassigned

Bug Description

the recent change of recheck/reverify comment_filter make it match with
the strings used by third party ci specific recheck commands like "recheck-ryu" and "recheck-vmware".
it effectively made it impossible to only re-run a third party ci.

Revision history for this message
Jeremy Stanley (fungi) wrote :

As far as I know there was never any intention in our design that you would be able to use "recheck" commands to trigger specific systems, and to date no standardized syntax for this has been proposed. I understand this has grown as an ad-hoc convention among some third-party CI systems, but no guarantees were made around supporting this.

Changed in openstack-ci:
status: New → Opinion
Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :

Jeremy,

ok, sure. but it was a quite useful functionality. just IMO.

Revision history for this message
Jeremy Stanley (fungi) wrote :

While I don't think this is a bug, it's worth discussing a concrete syntax for this which can be consistently implemented across multiple participating CI systems, preferably without overloading the currently ambiguous "recheck" syntax. I would suggest that this probably depends on completing Anita's CI account naming standardization efforts first, however, and then should be taken through proper Infra design channels by interested parties (perhaps the unofficial Third-Party CI team would like to collaborate on a proposal).

Revision history for this message
Jeremy Stanley (fungi) wrote :

This is also being discussed in http://lists.openstack.org/pipermail/openstack-infra/2014-August/001681.html for those who wish to chime in.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.