Age | Commit message (Collapse) | Author | Files | Lines |
|
File modes were not being preserved using the python tool, hence
manually unpacking and re-packing now into tar.gz
Change-Id: I40289117ec74ea2717a2428e9542da3dc98f590e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I0c8adbca67e5f2235bb2d48c19edc0f96400faab
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Changes Include:
- Fixes phase jobs to run on the same node
- Removes using WORKSPACE/.tmp dir for unpacking snapshot since other
phase jobs will need access to these files. Now just unpacks to cache
directory
- Fixes download for ODL. The previous way ODL was being downloaded
was only if a manual patch-set job was run on the ODL gerrit. This
patch changes the download to use the zip artifact automatically
produced.
- The zip artifact is converted to tar.gz and stored in /tmp/ for the
install job to consume. Note: the conversion is done because the
odl-pipeline install scripts only currently accept tar.gz.
- Extra checks in install job to make sure required files exist and
have been previously unpacked by deploy job.
Change-Id: I38aad98cac247eb4af2839811388b119079bc7ba
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Workspace wiping was done in builders, which can be removed in favor of
wiping workspace via the 'scm' entry in the job. For now we point at
apex since we require apex repo to clean the host properly. We also
need sdnvpn for the python code to upgrade ODL. Since we can only use a
single scm at a time, we use apex in the jjb, and then manually clone
sdnvpn in the builders that require it.
Change-Id: I52274fc8fdd6b6c052e396c2a63dab5abcbf764e
Signed-off-by: Tim Rozet <trozet@redhat.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: I61de7763412d791bcce20174d6058acf818d0e13
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
Due to not cloning the repos, the workspace is not wiped out.
This change makes sure we remove everything in workspace to
prevent jenkins from complaining.
Change-Id: Ife3c4c752cf37c6ff3bfcdea6ffaebc72c440373
Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
|
|
We do not need to clone netvirt repo as we are only interested
in the artifact.
Netvirt artifacts are removed from ODL Jenkins due to ODL Jenkins
artifact retention policy. This change ensures that we do not proceed
with the rest of the jobs if the artifact does not exist.
Change-Id: I9d8af28f5829fc9688c76f116d0bad737a9ecab6
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>
|