[openstack-dev] [tripleo] Testing optional composable services in the CI
emilien at redhat.com
Wed Aug 24 18:39:43 UTC 2016
Ok I have PoC ready for review and feedback:
- First iteration of scenario001 job in TripleO CI:
I checked, and the job is not triggered if we don't touch Sahara files directly.
- Patch in THT that tries to modify Sahara files:
I checked, and when running "check experimental", the job is triggered
because we modify puppet/services/sahara-base.yaml.
So the mechanism is in place (experimental status now) but ready for review.
Please give any feedback.
Once we have this mechanism in place, we'll be able to add more
services coverage, and run the jobs in a smart way thanks to Zuul.
On Wed, Aug 17, 2016 at 3:52 PM, Emilien Macchi <emilien at redhat.com> wrote:
> 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
>>> This is in addition to periodic jobs you're proposing, not replacing them.
>> 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:
> 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
> Emilien Macchi
More information about the OpenStack-dev