11 Commits

Author SHA1 Message Date
Cedric Brandily
4575e8fb95 Add test-results to check-neutron-dsvm-api job
Change-Id: I5ce5503025566cfbeb083bb023ce1b36d877e3b2
2015-04-08 13:55:36 +02:00
Akihiro Motoki
9e31aaf6db Enable Neutron in neutronclient functional test job
nova-network is used in python-neutronclient functional test job now.
No endpoint is configured for Nuetron, and neutronclient funcational
test will fail completely.

Change-Id: I00e56cab162941bb9d9bd84d0fffd66e9698bb4c
Related-Bug: #1429289
2015-03-12 19:04:36 +09:00
Jenkins
5752d28307 Merge "Remove use of DEVSTACK_GATE_TESTR_ARTIFACT_TARGET" 2015-03-10 18:46:13 +00:00
Jenkins
77478f0e93 Merge "Move neutron api job definition to neutron.yaml" 2015-03-09 21:41:20 +00:00
Kyle Mestery
7cf82434ce Add functional test job for python-neutronclient
Create a functional test job for python-neutronclient, set as non-voting
until its working. The neutronclient functional tests wil come from the
tempest cli tests.

Change-Id: I539eab368a4387b9ca9d795fc017bc2c3977202f
Related-Bug: #1429289
2015-03-09 19:33:43 +00:00
armando-migliaccio
9587736a3e Flip the bool condition
Otherwise we get in the if branch even when we don't want to.

Change-Id: I0aedeff743af61fef22f4b8e9028cb2c16eccc67
2015-03-06 07:40:35 -08:00
armando-migliaccio
c4acc672fb Fix the Neutron functional job for stable branches
Change e06c18 caused the Neutron functional job to break for
stable branches. Even though the change was careful to avoid
the breakage, it looks like the test:

[[ ! $BRANCH_OVERRIDE =~ ^stable/(icehouse|juno)$ ]]

led to setting DEVSTACK_GATE_PROJECTS_OVERRIDE, even for stable
branches (as shown during the failed runs, e.g. [1]), thus
breaking the functional job.

This patch use the right variables instead.

[1] http://logs.openstack.org/73/161273/1/check/check-neutron-dsvm-functional/56af914/console.html#_2015-03-05_00_26_21_129

Change-Id: I9c12f57b26e97da73364a6139a6e913f88e7f2d2
2015-03-05 09:21:10 -08:00
Maru Newby
f450aee025 Remove use of DEVSTACK_GATE_TESTR_ARTIFACT_TARGET
The intention was to have this variable allow functional jobs to reuse
the code used to archive testr artifacts for tempest, but the
requirement to have testr installed system-wide (or specify a target
venv where it is installed) let to pursuing use of project-config's
run-tox.sh script instead.

Change-Id: Ib932423bbeec76ae49b93e28e9fc693d7ee57bed
2015-03-04 21:00:36 +00:00
Maru Newby
db89c95d7b Move neutron api job definition to neutron.yaml
The convention seems to be including job definitions for a given
project in a single file rather than requiring a file per job
definition, so this change moves the neutron api job definition to
neutron.yaml.

Change-Id: I47649b3137a8ad15e29e521c786cee34a0de05ea
2015-03-04 20:55:11 +00:00
Maru Newby
e06c180c1d Limit target projects for the neutron func job
The neutron functional job does not rely on repositories other than
devstack and neutron, so limit the projects that devstack-gate updates
in the workspace accordingly.

This change also reverts the changes to the neutron api job that
validated that the functional job could safely run with a restricted
set of projects.

Change-Id: Ic59c3b2cc5d0b40a8f05c2d89eb1cf5e9e2f0d1d
2015-02-27 18:22:57 +00:00
James E. Blair
52051c9d67 Rename functional files to projects.
Generally this area of the repo is organized by project, so rename
the *-functional.yaml files to avoid the suggestion that each job
needs its own file.  Instead, name them for their projects to suggest
that you can look in each project file to see the jobs that apply
specifically to that project.

Change-Id: I31e95a405c03c207e26f9a63403e1b7205595b7f
2015-02-24 10:17:03 -08:00