Howdy, First of all, thanks for the creation of this space to discuss about shouldn’t be something common(in an utopia) but it’s part of our daily duties. I’m not sure if this is the right venue but I discovered today that the current implementation of the job for coverage[1] only valides the creation of the report and it doesn’t guarantee that the code coverage percentage drops (we’re relying on code reviewers to avoid that). I’m wondering if we could propose something to openstack-infra for enabling a threshold on the gates.
Regards, Victor Morales irc: electrocucaracha [1] https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/python-jobs.yaml#L17 PS: Congrats Ihar for your new role From: "Armando M." <arma...@gmail.com> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Date: Tuesday, January 31, 2017 at 1:47 PM To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev@lists.openstack.org> Subject: [openstack-dev] [neutron] Neutron CI team meeting Hi folks, Recently [1], a new meeting has been setup to give the neutron team a dedicated time to discuss any upstream CI matter (gate issues, testing strategies, etc), as well as an overflow space to be used after the main team meeting section [3]. Kudos to Ihar for being our first chair. Needless to say, attendance is welcome. Cheers, Armando [1] https://review.openstack.org/#/c/426311/ [2] https://wiki.openstack.org/wiki/Meetings/NeutronCI [3] https://wiki.openstack.org/wiki/Network/Meetings#Bugs_and_Gate_issues __________________________________________________________________________ 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
