Re: [openstack-dev] [Fuel] Plugins repositories moved to stackforge

2015-01-29 Thread Alexander Kislitsky
CI is requirement only for certified plugins. Is CI part of Fuel CI or not depends only on the plugin. In some cases we just can't run plugin CI on Fuel CI environment. On Thu, Jan 29, 2015 at 1:03 PM, Aleksandra Fedorova wrote: > Do we have a plan to enable CI for this repositories? Tests to r

Re: [openstack-dev] [Fuel] Plugins repositories moved to stackforge

2015-01-29 Thread Aleksandra Fedorova
Do we have a plan to enable CI for this repositories? Tests to run on commits, nightly builds, integration with nightly system tests? Should it be part of Fuel CI or completely independent? On Thu, Jan 29, 2015 at 11:55 AM, Alexander Kislitsky wrote: > Hi, guys > > All our plugins repositories

[openstack-dev] [Fuel] Plugins repositories moved to stackforge

2015-01-29 Thread Alexander Kislitsky
Hi, guys All our plugins repositories are moved to stackforge. Each plugin has separate repo and now can be maintained independently from core product cycle and without core-team attraction. Here is a map of migration: https://github.com/stackforge/fuel-plugins/tree/master/external_glusterfs ->