Age | Commit message (Collapse) | Author | Files | Lines |
|
Changes Include:
- Adds a daily job to create Apex snapshot tarball if functest passes
- snapshot artifact uploaded to artifacts.opnfv.org
- snapshot artifcat info is stored in snapshot.properties
- 3rd party job updated to deploy from snapshot
- 3rd party install netvirt job updated to use updated sdnvpn tools
JIRA: APEX-364
Depends-On: I792db0fac3f4e81969fe85c05fc298fe5af02537
Change-Id: I8a875c081d756d098173c0baf11c0b4e4956b9fd
Signed-off-by: Tim Rozet <trozet@redhat.com>
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
If scripts are used by hand and
WORKSPACE is not set then rm -rf /*
will remove the filesystem.
Change-Id: I9bb9ee6643d3916fedc7d3848ecf9b03bde10fae
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@ericsson.com>
|
|
Change-Id: I022acf23984a8d1a19a5e6e180178ee1d2e18480
Signed-off-by: Nikolas Hermanns <nikolas.hermanns@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>
|
|
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>
|