Hi All, I'm working on Third Party CI for Cinder and I've got several issues with Zuul configuration.
Third Party CI should run dsvm-tempest-full job to test Cinder driver in my case. It means, that all components should work well, not only Cinder. E.g.: I'm working on Cinder + Ceph integration CI. It requires that RBD-related code in Nova works well. https://bugs.launchpad.net/nova/+bug/1352595 breaks my Cinder CI with Ceph backend last week. So, it looks like I need to setup Cinder Third Party CI with Ceph backend for Cinder and Nova projects. But there are no needs to test Nova with Cinder and Ceph for every Nova commit. I'm looking for something like following: 1) run my Third Party CI for all patch-sets in Cinder 2) run my Third Party CI (Cinder + Ceph backend) for Nova only if it changes nova/virt/libvirt/rbd.py module. Does such approach acceptable for Third Party CI? If yes, does Zuul could handle such kind of triggers? Regards, Ivan Kolodyazhny, Software Engineer, Mirantis Inc.
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
