Age | Commit message (Collapse) | Author | Files | Lines |
|
We fixed the issue of accessing database failed on intel-pod8.
Some problem happened in Huawei Munich Lab.So we move the CI job to this pod.
Change-Id: Iefddcf2bef2cc296b1abd2d224b78c6dbc522295
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
Intel POD dedicated to VSPERF was moved to new location
and renamed to Intel POD 12.
Change-Id: I98a2204de90f6a491edb9e378da46600d4f29978
Signed-off-by: Martin Klozik <martinx.klozik@intel.com>
Reviewed-by: Aric Gardner <agardner@linuxfoundation.org>
Reviewed-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
|
|
The jenkins slave arm-build2 was retagged from opnfv-build-arm
to opnfv-build-enea. This change was made to avoid confusion, as
this slave is an x86 machine building an iso that is used by armband
Change-Id: Iac4e9bf635c128070c32818874626a81a28e6cf7
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
Add default settings for installer and slaves
Use baremetal deployment for daily
Use virtual deployment for merge
JIRA: DAISY-27
Change-Id: Ia00343225656c02aa292ee89d153f2e047c994b0
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|
|
This patch enables kvmfornfv verify test and daily jobs. As kvmfornfv
is assigned with Intel-pod10 for running the test cases, slave-label
for test phase is also modified.
Change-Id: I5202db7c6eeeec5a92266c1bfc7b8d3e46dc33a4
Signed-off-by: Gundarapu Kalyan Reddy <reddyx.gundarapu@intel.com>
|
|
This patch adds two pods deployed by fuel and joid,
also adds non-voting jobs on fuel pod (ool-virtual2).
Change-Id: I5dbadbbeaebf75bb27930233d2609adbc2757ca5
Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
|
|
The builders are left empty until after the further discussion and
they will be fixed in a separate change.
Change-Id: Iad585d43620e9956fd3b2b3406a5b01ec51b8822
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I320b37ed0897844c9f68c1ea75e4d8cfb92c6932
Signed-off-by: meimei <meimei@huawei.com>
|
|
Change-Id: Ia6c544901fb9c7c434104c095b9e2f173f7f5571
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: I2992bda320f7c7b17b554539943713c6dc13d858
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: Ide4d879106683a9adab5ea4bf195982eadf6bcb8
Signed-off-by: meimei <meimei@huawei.com>
|
|
Change-Id: Ie3ebf31fda67ca04cc8f6ebb86a635ecb2e82d51
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
For the functest change we use the new cli which provides us
with comma seperation of the test cases.
Change-Id: Id6c88bd3e13ecce7bf5a738ead8ad98df4e00b5a
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
|
|
Change-Id: I073a27045db93fcf3c9906abe1c18ad3d26743b2
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This is a temporary fix in order to continue with the netvirt parts.
Once Apex team finishes their work with APEX-360, this job will be
aligned with it.
The job to bring up apex vms will be run on ericsson-virtual5.
The rest of the jobs will run on ericsson-virtual6, which is virtual
jumphost for the apex environment.
Apart from this, the job can now be (re)triggered by putting keyword
opnfv-test on ODL Gerrit.
There are still flaws and things to improve with the jobs such as
finding out if the downloaded artifact is real or just a file not found
response from ODL Jenkins and so on but these will be fixed later.
Change-Id: Ie38e513df08c6c76eacee53a112c09171b1f6c7d
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Change-Id: Ia105d32133c5b2df3bea363ff8cb94b2984fb172
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
This change creates basic job structure for ODL netvirt testing in OPNFV.
The job should be triggered once the below job is completed
https://jenkins.opendaylight.org/releng/job/netvirt-patch-test-current-carbon
and fetch the artifact that is already built by the job. The build result
codes OPNFV is interested in are SUCCESSFUL and UNSTABLE.
Once the job gets triggered, the build URL will be fetched from ODL Gerrit using
Gerrit REST API and the artifact will be downloaded from ODL Jenkins.
The downloaded artifacts will then be installed on the Apex environment.
There are 3 points that need to be highlighted.
- The Apex environment will be created using the promoted snaphots/qcow2
images and already deployed VMs will be brought up. See below for the details.
https://jira.opnfv.org/browse/APEX-360
- The hardcoded values in download-netvirt-artifact.sh are there to get the
basics in place. (branch name, job name, etc.) Once things work as expected,
they will be made dynamic.
- A workaround using Gerrit REST API is put in place to get build number of the
job netvirt-patch-test-current-carbon to download the artifact.
The reason why we use Gerrit REST API is that the OPNFV Jenkins has an older
version of Gerrit Trigger Plugin which lacks feature that injects review
comments as environment variables. Upgrading Gerrit Trigger Plugin will not
help either since OpenStack JJB does not support the new version of Gerrit
Trigger Plugin and does not generate the new job XML.
JIRA: RELENG-171
Change-Id: I7ff8c5809dcb2e8ffa5c7c5aeb9cdf70e4e7e2f4
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Individual project jobs can now be tested using:
jenkins-jobs test -r jjb/global:jjb/$project
- Rename '.yaml' files to '.yml' so they get checked by the
verify-releng.sh script, and update the script to include checking of
'.yaml' files.
- Move parameter and macro files under new 'global' directory.
Change-Id: I6b74f5d8af2bced3256a7f4a33983df5310511a2
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|