Hi Matt,

My guess is that 'all' now includes plugins?

Yes, 'all' should run Tempest plugins too.

https://opendev.org/openstack/tempest/src/branch/master/tox.ini#L67-L83 67 │ [testenv:all-plugin] 68 │ # DEPRECATED 69 │ # NOTE(andreaf) The all-plugin tox env uses sitepackages 70 │ # so that plugins installed outsite of Tempest virtual environment 71 │ # can be discovered. After the implementation during the Queens 72 │ # release cycle of the goal of moving Tempest plugins in dedicated 73 │ # git repos, this environment should not be used anymore. "all" 74 │ # should be used instead with the appropriate regex filtering. 75 │ sitepackages = True 76 │ # 'all' includes slow tests 77 │ setenv = 78 │ {[tempestenv]setenv} 79 │ OS_TEST_TIMEOUT={env:OS_TEST_TIMEOUT:1200} 80 │ deps = {[tempestenv]deps} 81 │ commands = 82 │ echo "WARNING: The all-plugin env is deprecated and will be removed" 83 │ echo "WARNING Please use the 'all' environment for Tempest plugins."

-- Masayuki Igawa Key fingerprint = C27C 2F00 3A2A 999A 903A 753D 290F 53ED C899 BF89

On Thu, May 16, 2019, at 02:21, Matt Smith wrote:

Hey Folks,

First time posting to the mailing list, so hopefully I got this right.

Anyways, Tempest complains when I use 'all-plugin' and says it's deprecated. Cinder has Tempest plugins that were triggered by using 'all-plugin' instead of 'all' and now I don't know how I'm supposed to run those plugins as well.

My guess is that 'all' now includes plugins? Or maybe there's an alternative for running plugins?

Regards,

Matt

---

Matthew Smith Software Engineer mss@datera.io 214-223-0887