Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I83aafd2cf6317efefaa4b4208b286d5d26231767
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.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>
|
|
|
|
JIRA: ARMBAND-366
Change-Id: I6b513b6775b612bcc30327535e71827a7dd36ed9
Signed-off-by: Delia Popescu <delia.popescu@enea.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>
|
|
|
|
Change-Id: I5312ac784b1621ce968bbdfb1532859dada0e790
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Openstack APIs response call is tacking very long on ARM
Work is being done on fixing the issue
Temporary increase functest timeout on x86 too because of COMPASS
JIRA: ARMBAND-366
JIRA: COMPASS-589
Change-Id: I355500da56c5a040324c0969237ac2decfd29edf
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
|
|
Variables injected by envInject are set after the job variables
which results in not setting the variable correctly. The Jenkins
test script now uses the variable injected by envInject to set
the INSTALLER_TYPE to XCI_INSTALLER.
Change-Id: Id79281a2ee22d407ffb1bd7c4be1471f6f329803
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
We need to work on functest healthcheck for Kubernetes scenarios.
Until we get it working, healthcheck is disabled.
Change-Id: If470dbe956c5859825f0829d1f8d022bdafcc242
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Only one scenario job can be excuted in the same POD. The rules should
be configured in job teamplate instead of parent job.
Change-Id: I9f672345985dbfdfe54b9ccd017a3a575a2ab412
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
Change-Id: I54b4015b1da9a5961c2d3ee1f672b381a3f72914
Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
|
|
Change-Id: Ifbe676cd347c2d3c68f04b5137f3ccaa83a95894
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
The scenarios named os-* are deployed by osa and the ones
named k8-* are deployed by kubespray. This change determines
the installer to use by looking into the scenario name.
The installers are currently hardcoded within xci-set-scenario.sh
script and this needs to be fixed for other installers when they
onboard to xci.
Apart from setting the installer, extraction of generic and external
scenarios are moved into corresponding functions.
Change-Id: I19882bcd2a1260765e601ecbe517551c60401d74
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
|
|
We do the VM cleanup as part of the postbuild process so we do
not need to have it in the functest jobs anymore.
Change-Id: I64e4b58837090df33ae529232ef15a19de8f198a
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
In
https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170,
it indicates that:
only build parameters that have been explicitly defined in a job's
configuration will be available by default at build time. Any other
arbitrary parameters added to a build by plugins will not be
available by default.
It has been tested in sandbox.opnfv.org that only defined parameters can
be passed to the triggered jobs.
For parameters required by TESTAPI are common to all the projectes,
including installers, Functest, and Yardstick, it is convenient to
define a common macro and used by others.
Change-Id: Iac1da85445e1b5d75109ccd64b174f35151b9969
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
Change-Id: I4b30765b243e2a1a6d2079b71fc6d18c14853dec
Signed-off-by: 00184532 <lu.yao135@zte.com.cn>
|
|
Change-Id: I44c47347ce8759a545245bf2d3ad6d6657226875
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
Switching to multijob forces to increase executors which is too risky
so closed to the release.
It basically reverts the previous functest-daily-jobs.yml [1].
[1] git checkout 7f06f9492f4f8dd47669a553ef6e9c967fa29e8e jjb/functest/functest-daily-jobs.yml
7f06f9492f4f8dd47669a553ef6e9c967fa29e8e
Change-Id: I4a461108b11effe59e49108e1d95a9aae6e81ade
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|