Open Stack

i'd be in favour of dropping the full cases -- never really understood 
why we ran all the tests everywhere. ceilometer/aodh are present at the 
end of the workflow so i don't think we need to be concerned with any of 
the other tests, only the ones explicitly related to ceilometer/aodh.

On 12/04/2016 8:12 AM, Ryota Mibu wrote:
> Hi,
>
>
> Can we disable 'full' tempest tests for ceilometer?
>
>      - gate-tempest-dsvm-ceilometer-mongodb-full
>      - gate-tempest-dsvm-ceilometer-mysql-full
>      - gate-tempest-dsvm-ceilometer-mysql-neutron-full
>      - gate-tempest-dsvm-ceilometer-postgresql-full
>      - gate-tempest-dsvm-ceilometer-es-full
>
> We've merged ceilometer test cases from tempest repo to ceilometer/aodh repo as tempest plugin [1-2].
> So, I suppose we can disable these jobs for ceilometer checks and gates, once we enabled ceilometer tempest tests with migrated codes [3].
>
> But, it will stop other tempest tests not in ceilometer dir of tempest in gate jobs for ceilometer, as current setup is to kick 'full' tempest tests even for ceilometer changes.
> Let me know if there is any problem.
> I might miss the original intention of Jenkins job setup for ceilometer.
>
> [1] https://blueprints.launchpad.net/ceilometer/+spec/tempest-plugin
> [2] https://blueprints.launchpad.net/ceilometer/+spec/tempest-aodh-plugin
> [3] https://review.openstack.org/#/c/303921/
>
>
> Thanks,
> Ryota
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

-- 
gord