Hi all, As part of the effort of splitting tempest plugins to their own repositories [0], we are calling all Manila 3rd party CI maintainers to adjust their gate scripts to use the new tempest test repository
If the third party CIs are configured to run with DevStack Gate, they only need to make a one line change to their gate scripts, manila-tempest-plugin can be installed and configured by Devstack gate prior to Devstack by using the "PROJECTS" variable, for example: export PROJECTS="openstack/manila-tempest-plugin $PROJECTS" This is how we used to set up python-manilaclient, so: export PROJECTS="openstack/python-manilaclient openstack/manila-tempest-plugin $PROJECTS" For those that are not using DevStack gate, you could just do this before Devstack: git clone https://git.openstack.org/openstack/manila-tempest-plugin /opt/stack/manila-tempest-plugin sudo python /opt/stack/manila-tempest-plugin/setup.py develop Both these methods will clone and install manila-tempest-plugin from git.openstack.org into $DEST/manila-tempest-plugin. We intend to make this change [1] effective after next weekly meeting, on Thursday 14th. It is important to note that CI mainteiners can make this change right away and it would not break CIs when this patch merges since all manila tempest tests are available in the new repo. Thanks, Victoria [0] https://governance.openstack.org/tc/goals/queens/split-tempest-plugins.html [1] https://review.openstack.org/#/c/512300/
__________________________________________________________________________ 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
