Age | Commit message (Collapse) | Author | Files | Lines |
|
It adds a new env var STORAGE_PROTOCOL to override storage_protocol
in tempest. The default value is unchanged [1].
[1] https://docs.openstack.org/tempest/latest/sampleconf.html
Co-Authored-By: Viktor Tikkanen <viktor.tikkanen@nokia.com>
Change-Id: I19e4e25212b6f6176e3b967e01eb634c15e4d474
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
(cherry picked from commit a561c6ca316feb1a203327aa729ac0317f70df48)
|
|
Change-Id: Ide63c601b50ec2f6f02ef2682035b937ca2a1662
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Change-Id: I409975acd1493e2f5a6bdcb3a4bd6ff6e383e02e
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
It allows loading functest and functest-kubernetes jjbs in one
Jenkins.
Change-Id: Ia52e84583bc25aad0d1508096b536cbd5585d261
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
As opposed to the Releng ones, they are designed to be easily
executed by endusers as well. They can be considered as a first step
towards a full Functest CI/CD toolchain deployed via docker-compose.
All components testcases are enabled here.
They hugely leverage on templates to load the right yamls per branch
and multijobs to run testcases in parallel. Many steps are proposed
allowing running part of the chain.
Executors have to be increased to allow running them (it was tested
vs 10 and more).
At first, all docker images are downloaded to avoid different
versions between testcases.
They will be improved in a second change to ensure that only one node
is selected and to take all Functest env vars into account.
Change-Id: I99c7b8ee5d0ddbb00102b3147739b5e8b5c65c23
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|