Use for samples testing separated job

Samples testing has to go over all files and ensures that all tasks
have proper specs which is time & disk comsuing, it takes up to ~10-15 seconds

However, testing samples is not required in most development cases, only when
new plugins are added, so it makes sense to split it in separate job

Change-Id: I3536226c389fec0f41d84325747dd0f8b6a880f6

tox.ini

@@ -1,7 +1,7 @@
 [tox]
 minversion = 1.6
 skipsdist = True
-envlist = py35,py34,py27,pep8
+envlist = py35,py34,py27,pep8,samples
 
 [testenv]
 extras = {env:RALLY_EXTRAS:}
@@ -67,6 +67,12 @@ commands =
   find . -type f -name "*.pyc" -delete
   {toxinidir}/tests/ci/rally_functional_job.sh {posargs}
 
+[testenv:samples]
+commands =
+  find . -type f -name "*.pyc" -delete
+  python {toxinidir}/tests/ci/pytest_launcher.py tests/samples --posargs={posargs}
+
+
 [testenv:cover]
 commands = {toxinidir}/tests/ci/cover.sh {posargs}
 

zuul.yaml

@@ -29,6 +29,14 @@
     vars:
       tox_envlist: self
 
+- job:
+    name: rally-tox-samples
+    parent: tox
+    description: |
+      Validates rally/samples
+    vars:
+      tox_envlist: samples
+
 - project:
     check:
       jobs:
@@ -36,6 +44,7 @@
         - rally-install-ubuntu-xenial
         - rally-install-centos-7
         - openstack-tox-functional
+        - rally-tox-samples
         - rally-tox-self
     gate:
       jobs:
@@ -43,4 +52,6 @@
         - rally-install-ubuntu-xenial
         - rally-install-centos-7
         - openstack-tox-functional
+        - rally-tox-samples
         - rally-tox-self
+