Age | Commit message (Collapse) | Author | Files | Lines |
|
It is difficuly to have post-merge jobs per scenario since we set
the scenario during job runtime and having jobs per scenario makes
things unnecessarily complicated. Apart from that, there is no
reason to have scenario specific merge jobs either since this is
some kind of verify job and everything is same except the scenario
name itself which we extract via set-scenario script.
Daily and further jobs will be scenario specific since they will
be run on timer and we will have ability to specify the scenario.
Change-Id: I3bf6d5ce0fbc48b2d2b2b9695e198bad229ce08d
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
|
|
|
|
PROJECT_NAME is added into scenario metadata to use for promotion and xci dashboard.
Also, the metadata collected is aligned across different type of patches including
the skipped ones.
Change-Id: I3751884b48f5d9306d0cae35c757b976484b26a3
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
|
|
|
|
We need to enter the $HOME/releng-xci/xci directory instead of
/root/relneg-xci/xci since we are ssh'ing as 'devuser'.
Change-Id: Id05d5012d58443c7f415a58f9f3d1ae16fd25b55
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Change-Id: Ic9801a2f1282b695025a6dce70e662765ce4296b
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
1. Add 'set +e' before running k8s tests, then the following builder
of functest-store-results will be executed.
2. Remove the logic of managing k8s scenario from functest-alpine.sh
Change-Id: I9a269fc46e45d1db6af741775d475e887ebc79c7
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
Change-Id: Id1ac133782e6b90929ddc055efbc6997ff63adc2
Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
|
|
|
|
Change-Id: I81eaed8b397b5d748c5fde5a07dadecde0ec08fa
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
This patch is to online posca_factor_soak_throughputs testcase
Change-Id: Ief6776e224c59de600fbe44709c767aecd01d0f0
Signed-off-by: Yang Yu <Gabriel.yuyang@huawei.com>
|
|
This is to support sfc test on Compass:
https://gerrit.opnfv.org/gerrit/#/c/52825/
Change-Id: I77223363205dc8edd34de8a6c529e68d3b6a6442
Signed-off-by: Linda Wang <wangwulin@huawei.com>
|
|
|
|
|
|
|
|
Set Yardstick Jenkins job's parameter 'GIT_BASE' for overriding the default
GIT URL from Global Jenkins configuration.
Change-Id: I6fe4a67589aa391c5bc7ac4433509dcfcce858c6
Signed-off-by: trevortao <trevor.tao@arm.com>
|
|
|
|
Scenario names with 'upstream' in them will not download any artifacts
and deploy from upstream. For now, this even applies to the apex
python RPM for daily deployments. We will only use git repo for
daily until after Fraser.
Change-Id: I0da16dfde117ba6c1e7597294d8e4afc8501dd53
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
|
|
Changes coming to these do not impact the framework so there is
no need to run full verification for these.
Change-Id: Ia9f8f4772a94cb0761c49ff27933798265831fa4
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: Ide49917687ed583497ca089969fd2c7e7e00e548
Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
|
|
Change-Id: Ic914bc5bf11e2246f214990353c804688d6e43d9
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
JIRA: -
Compass installer has been containerized since OPNFV 5.0.
To enable SFC test cases in Functest for Compass installer,
a new adapter is needed to be compatible with both containerized
Compass installer and SFC test cases.
Change-Id: I4e1a9e5fcbec016a0c3fde77ace9c2cc677e3e4c
Signed-off-by: Yifei Xue <xueyifei@huawei.com>
|
|
This is for bottlenecks job online
Add a new testcase in compass daily
Change-Id: I4e09eef894e176bf4fa0df0969ef49f19444103e
Signed-off-by: liyin <liyin11@huawei.com>
|
|
From the CI results, ha.tc010 can't find the process named rabbitmq-server
for Apex, Compass and Fuel.
Try to change it to be rabbitmq.
Change-Id: Ibf8a9e1c7eeebbc306624fe926c139786b9833fb
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
|
|
|
|
This change lays down the basic job structure for post merge promotion
jobs. The job structure will be
- a top level multijob job that is scenario specific and can not run
concurrently. This job runs distro deploy and test jobs for all the
distros in the first phase concurrently, followed by a common promote job.
- the deploy and test jobs are same as the xci-verify jobs except the
trigger. They are triggered by top level multijob.
- the promote job is run once all the deploy & test phase jobs successfully
completed, uploading promotion metadata to artifacts.opnfv.org.
The builders except set-scenario are left empty in order to try the basic
job setup first. Followup changes will get real things in.
Once the basics are in place, the first promotion will be done using functest
healthcheck and then we will start working on gating scenarios for promotion
using functest smoke and perhaps feature test cases.
Change-Id: Ib91ffe0f3003b86841a62537c52fde176cafa70f
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
When functest fails, the job exits directly without us logging the
functest output to console. [1] Grepping functest log for FAIL for
determining the result helps us to cat the log before exiting with
right exit code.
[1] https://build.opnfv.org/ci/job/xci-verify-ubuntu-healthcheck-virtual-master/509/console
Change-Id: I01e3dcc51321e935b1722b749e8caf7ec5ad755b
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
|
|
1. change the path of all images
2. remove the sdnvpn special envs
This patch should be merged after these 2 patches.
1. https://gerrit.opnfv.org/gerrit/#/c/53395/
2. https://gerrit.opnfv.org/gerrit/#/c/53757/
Change-Id: Ie1dc9388be52629c5fcc0ef893963c4de2c72491
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Build and push xtesting images
Create manifests for xtesting images
Build xtesting images for arm
JIRA: FUNCTEST-948
Change-Id: I3fbe6cdfef5b304a45d76533417f3c4bc58dddbe
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
Change-Id: I454c327f3359688742b5d8c4299efee05d6494a2
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
|
|
It is not always practical to try determining scenario and installer
to run jobs programmatically. This change adds possibility to do that
by parsing commit message and skipping the automatic scenario and
installer extraction.
Change-Id: I10c9620fe8bb69a2d69fceb31d08084265aa1d75
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Fixes the following problem
[description-setter] Description set: Scenario: os-nosdn-nofeature | Node: intel-virtual14
[xci-verify-ubuntu-healthcheck-virtual-master] $ /bin/bash /tmp/jenkins7521920744845291696.sh
/tmp/jenkins7521920744845291696.sh: line 21: GERRIT_TOPIC: unbound variable
Build step 'Execute shell' marked build as failure
Change-Id: Iddf82e6ae6c6c433d941c461953c11935bc45269
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
Patrole is now integrated in smoke and the dedicated container is
being removed [1]
[1] https://gerrit.opnfv.org/gerrit/#/c/53659/
Change-Id: Ifb1989c5e430a4bf0fdd553f2e3e82f69a704f25
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Sometimes we make global changes that affect multiple components at
once and splitting that is not possible because it needs to be shipped
as an atomic change. As such, allow topics with 'force-verify' to run
the CI using the default installer and scenario.
Change-Id: Ie4753822111b20c4f479886a55fe569c9b91ccd0
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
1. Run test suite ovp.1.0.0 on Apex with even 'BUILD_NUMBER'
for scenario nosdn-nofeature and bgpvpn.
2. Run test suite proposed_tests on Apex with odd 'BUILD_NUMBER'
for scenario nosdn-nofeature and bgpvpn.
JIRA: DOVETAIL-611
Change-Id: I5d4a86242d633eb83ddb0939dff5cf617c971c3b
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|