Age | Commit message (Collapse) | Author | Files | Lines |
|
BRANCH is useless in case of components which only inherits from tempest.
The build could simply fail depending on the docker version [1].
[1] https://build.opnfv.org/ci/job/opnfv-functest-components-latest-build/1/console
Change-Id: I7fe0c5bf8373e61a658153fda3d3a4bd233f6bc0
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
(cherry picked from commit 284e30415fdec9c1a17c7f0b0b023fb0bbf045ce)
|
|
It eases foctorizing between releng (1 multijob only) and functest
jjbs.
Change-Id: I72deb86d155a1da7e0d8bf0f76992e7b6dd6cfad
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
(cherry picked from commit 5a846fceeeb61b8586ab28f1d48322434cdb67a4)
|
|
It also updates all jobs and fixes Dockerhub hooks.
Change-Id: Ib182155736b4dbdb829293081741a9d5cb8ea6d7
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>
|