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

Steven Hardy shardy at redhat.com
Thu Aug 25 13:16:29 UTC 2016

On Wed, Aug 17, 2016 at 07:20:59AM -0400, James Slagle 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.

+1 I think this sounds like a really good idea.

Now that we're doing almost all per-service configuration in the respective
templates and puppet profiles, this should be much easier to implement I
think so definitely +1 on giving it a go.


More information about the OpenStack-dev mailing list