[openstack-dev] [Designate] Tempest Tests - in-repo or separate
graham.hayes at hpe.com
Mon Apr 4 15:41:48 UTC 2016
On 04/04/2016 16:36, Jordan Pittier wrote:
> On Mon, Apr 4, 2016 at 5:01 PM, Hayes, Graham <graham.hayes at hpe.com
> <mailto:graham.hayes at hpe.com>> wrote:
> As we have started to move to a tempest plugin for our functional test
> suite, we have 2 choices about where it lives.
> 1 - In repo (as we have  currently)
> 2 - In a repo of its own (something like openstack/designate-tempest)
> There are several advantages to a separate repo:
> * It will force us to make API changes compatable
> * * This could cause us to be slower at merging changes 
> * It allows us to be branchless (like tempest is)
> * It can be its own installable package, and a (much) shorter list
> of requirements.
> I am not a Designate contributor, but as a Tempest contributor we
> recommend to use a separate repo. See
> for more details.
Yeap - that was one of the reasons I will leaning towards the separate
repo. The only thing stopping us was that I cannot see any other project
who does it 
We just had a quick discussion in IRC and we are going to go with
the separate repo anyway.
> If everyone is OK with a separate repo, I will go ahead and start the
> creation process.
> - Graham
> 0 - https://review.openstack.org/283511
> 1 -
> OpenStack Development Mailing List (not for usage questions)
> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
More information about the OpenStack-dev