[openstack-dev] [tripleo] Testing optional composable services in the CI

Emilien Macchi emilien at redhat.com
Wed Aug 17 19:52:03 UTC 2016


On Wed, Aug 17, 2016 at 7:20 AM, James Slagle <james.slagle at gmail.com> wrote:
> On Wed, Aug 17, 2016 at 4:04 AM, Dmitry Tantsur <dtantsur at redhat.com> wrote:
>> However, the current gate system allows to run jobs based on files affected.
>> So we can also run a scenario covering ironic on THT check/gate if
>> puppet/services/*ironic* is affected, but not in the other cases. This won't
>> cover all potential failures, but it would be of great help anyway. It
>> should also run in experimental pipeline, so that it can be triggered on any
>> patch.
>>
>> This is in addition to periodic jobs you're proposing, not replacing them.
>> WDYT?
>
> Using the files affected to trigger a scenario test that uses the
> affected composable service sounds like a really good idea to me.
>

I have a PoC, everything is explained in commit message:
https://review.openstack.org/#/c/356675/

Please review it and give feedback !

>
> --
> -- James Slagle
> --
>
> __________________________________________________________________________
> 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



-- 
Emilien Macchi



More information about the OpenStack-dev mailing list