Hi, In yesterday's meetup, we discussed how we could help 3rd party CI become all green (ie, not fail). One of the suggestions was to have the gate status available. Among other things, this would help developers know whether they should (or shouldn't) ignore gate failures for 3rd party CI.
We've put in place a similar process for 3rd party CIs, as we have been doing for ironic CIs: 1. There is a section in our main etherpad [2] for mentioning failures. 3rd party CI maintainers, please try to keep that up to date. 2. There is a separate etherpad [3] to capture all failures, discussions of, and what their resolutions were. The data should prove useful, at the very least, so developers know what they should be looking out for, when reviewing :) Thanks! --ruby [1] https://etherpad.openstack.org/p/ironic-virtual-meetup, starting at L90 [2] https://etherpad.openstack.org/p/IronicWhiteBoard, starting around L50 [3] https://etherpad.openstack.org/p/IronicThirdPartyGateDebugging
__________________________________________________________________________ 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
