Barbican

Don't clone barbica-tempest-plugin automaticlly

Bug #1673686 reported by Nam
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Barbican
Won't Fix
Wishlist
Nam

Bug Description

When devstack enable tempest, the problem is that barbican does not clone the barbican-tempest-plugin repo automaticlly. We should fix it.

Nam (namnh)
Changed in barbican:
assignee: nobody → Nam (namnh)
summary: - Don't auto clone barbica-tempest-plugin
+ Don't clone barbica-tempest-plugin automaticlly
Revision history for this message
Dave McCowan (dave-mccowan) wrote :

WIP: https://review.openstack.org/#/c/446870/

Comment from kfarr:
The code to install barbican-tempest-plugin along with barbican was removed on purpose (I87bd021f08f381c5319ee7ffa08fb8026a22a16c). It was removed because a few other projects commented that they'd like to install barbican as part of their gate checks, but did not necessarily want to run the barbican tempest tests.

If you need to install barbican-tempest-plugin, it is recommended to install it manually, using:
  git clone https://git.openstack.org/openstack/barbican-tempest-plugin
  pip install -e barbican-tempest-plugin/

Changed in barbican:
importance: Undecided → Wishlist
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.