| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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>
|
Fatih Degirmenci
meimei
Nikolas Hermanns
Trevor Bramwell