Many of us are still working on setting up and testing 3rd party ci for cinder drivers.
None of them currently have gerrit +1/-1 voting, but I heard there's a plan to "disable" those that are "not working" post-J3 (Please correct me if I misunderstood). However, Post-J3 is a great time to work on 3rd party ci for a few reasons: 1. Increases the overall QA effort when it's most needed. 2. Many contributors have more time available since feature work is complete. Since erroneous failing tests from non-voting ci accounts can still distract reviewers, I'd like to propose a compromise: Marking 3rd party ci jobs still undergoing testing and stability as (non-voting). e.g. dsvm-tempest-my-driver<http://15.126.198.151/67/106567/30/check/dsvm-tempest-hp-lefthand/a212407> SUCCESS in 39m 27s (non-voting) dsvm-tempest-my-driver FAILURE in 39m 54s (non-voting) This way, progress can still be made by cinder vendors working on setting up 3rd party ci under 'real' load post J3 while minimizing distractions for cinder reviewers and other stakeholders. I think this is consistent with how the OpenStack "Jenkins" CI marks potentially unstable jobs. Please share your thoughts. Thanks, Ramy
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
