Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I2341191b9afbf7b572a6ae28a50eb722b66109c7
Signed-off-by: Yolanda Robla <yroblamo@redhat.com>
|
|
|
|
- cleanup deploy tooling for old-style artifacts (ISO-based);
- remove danube stream, related jobs and hacks required for them;
Change-Id: Ib2486173df1ec83f2dbc08a5e9faf950bffb4b06
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
We don't currently support ONOS and KVM-based scenarios.
Change-Id: I9869498c1f726293d571562291e850a817bf3e18
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I64aae5719f1a0a667e56722bab9e5012a813571f
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
Remove obsolete/breaking RETURN rule from preparation
stage of Yardstick and Dovetail test suites.
Change-Id: I817780da95f10bc12c491e56806455d1aee25ece
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Previously we created the branches over Gerrit's HTTPS interface. One or
two projects from the previous release did not have their stable
branches created at the correct place.
Switch to using ssh for branch creation will be more reliable and easier
for us to verify.
Change-Id: If7f24d2b19e74513b59889bd64d25919aa048e4c
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Some projects (e.g. Fuel, Armband) embed their own git submodules,
which are picked up by Sphinx during RTD verify job, leading to a lot
of issues (e.g. duplicate labels since Armband includes Fuel as a git
submodule of its own).
Change-Id: I771f7c95334fc25c82cc8b14ee2064b043d9e321
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
|
Change-Id: I09978a08d00c561f17ce3a7d5ba75d80aa49a0f6
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Add a scenario parameter for functest-k8s in container4nfv
project.
Change-Id: I1465ed268c7f5015616076cd8efc923fd833c623
Signed-off-by: Jingzhao Ni <jingzhao.ni@arm.com>
|
|
Else Fraser jobs are wrong [1]
[1] https://build.opnfv.org/ci/view/functest/job/functest-compass-baremetal-daily-fraser/lastFailedBuild/console
Change-Id: I4b3e1cacb9da3a3c51ec5b1be615bd2049b6a6e7
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
If there is a CI failure, then we need the VM to be present so we can
ssh to the slave and collect all the logs we can in order to debug
the problem. However, in order to not leave stale VMs around, we should
remove the VM if a job is scheduled again on the same node. As such, if
we need to debug a build on the node, we need to disconnect the node
from Jenkins so the VM is not wiped by a future job.
Change-Id: I93e7d7402fe03c392b63b87e7d438191f6e7e9cc
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
Our virtual node is kind of slow in handling all triggered tasks.
Change-Id: I1b4616561aaaabfe96ef77b4a649a16e888d18c0
Signed-off-by: Yibo Cai <yibo.cai@arm.com>
|
|
This reverts commit b4a65c5e6777a53be5ea817c967caeee51285a7f.
Chain of DOCKER-ISOLATION already has required rule.
Change-Id: Ic7d3e93a2814a42764b4822ef96e0841f68b774d
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
|
|
JIRA: ARMBAND-401
Change-Id: Icd32874ecb38c3f7469e71bd461794b65f50494c
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Docker build automatically appends 'amd64-<TAG>' or 'arm64-<TAG>',
which are normally combined using manifest tool. However, for verify
we don't push a manifest, so use the explicit arch-specific tag.
Change-Id: Idc036216919164e71d3da5032a79f7f47d115710
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I6b641c87e2672a9e879865baebfa3a58129823f7
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
|
|
|
|
|
|
|
* changes:
Create Gambia and Hunter Release Jobs
Create stable/hunter Branch for Functest repos
|
|
|
|
This is a temporary fix until we can determine the full list of
requirements from each project needed for the opnfv-build-ubuntu labled
servers.
Previously these were building fine on ericsson-build4, so reassigning
them there should keep there builds green.
Change-Id: I767b6faa718cd6dd4b9fd17f83e7ee817cfb8c4d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Change-Id: I22c05b0cb2973e84b6352a0ab4e7e38132e909f9
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
It manages stable/gambia and stable/hunter as well.
Change-Id: Ib259995f8f0e45767a51204c4eb6fd239e66ed92
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
This will create the release jobs needed for the OPNFV Gambia
and Hunter stable-stream release process.
Change-Id: Icdb9a337dcbad26fccb0e1e2935f8082f17bb220
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA: RELENG-408
Change-Id: Ie6ac842ebd1bb6264c88a7f8ee0446d76fc3dbdd
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
|
|
|
|
Rework Fuel verify jobs:
- split 'fuel-verify' into per-arch jobs (amd64 and arm64):
* for now, arm64 jobs are non-voting;
- add 'docker-build' phase job:
* the docker build job will run on the same virtual POD jump host
as the deploy, to bypass the need of pushing to a (public)
Docker hub registry - this might be refactored later to resemble
the old Fuel ISO build workflow where the artifacts built during
verify are the ones actually promoted - with the current method
the final build & tag (ran on OPNCI CI build servers) might yield
different results due to different docker build cache states;
* the locally built container image is tagged with the 'verify'
designator and not pushed to a public registry, only consumed
during verify's job 'deploy-virtual' phase;
JIRA: ARMBAND-401
JIRA: FUEL-383
Change-Id: I9b0d8079e759cdc895260219a8a4989411c995ff
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Please note that these triggers are temporary and they will be
adjusted to fit promotion based triggering. This will result
in running scenario deployments and testing if any scenario
has changes. Otherwise, daily jobs will be skipped.
Change-Id: I24e8c4d7f1da4d3203d81a8929ce2bc60d398ece
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
Change-Id: I2d0a71fc40a4a6cd1f5b1e63ca429c5b83b7ad00
Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
|
|
JIRA: BOTTLENECK-242
TEST_CASE is wrongly defined. Spaces should be deleted
in order to make the right defination for shell.
Change-Id: I981e80af8fc8dfd9f375b44b205f7478e0d4f260
Signed-off-by: Yang (Gabriel) Yu <Gabriel.yuyang@huawei.com>
|
|
https://build.opnfv.org/ci/view/functest/job/functest-compass-baremetal-daily-fraser/373/console
Change-Id: I8c76620c67c28ea3f14ff79aef98ad2815a3aaa9
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
JIRA: BOTTLENECK-242
Change-Id: I2fb92017b2b07ede448c817c89ae0d7572cfbae9
Signed-off-by: Yang (Gabriel) Yu <Gabriel.yuyang@huawei.com>
|
|
|
|
Daily jobs run on the actual slave so they leave virtualbmc processes
running even when the job is finished. As such, we need to make sure
that such artifacts are gone as soon as we start a new job.
Change-Id: I82f49279cc105e788db466e5040e6a31c537af5c
Signed-off-by: Markos Chandras <mchandras@suse.de>
|
|
|
|
|
|
As these only affect jobs defined in global-jjb (no other jobs used
these variable names) they should be safe to define at the global level.
Change-Id: I646c3afc73757bff561cc84b80df064e13680080
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Create functest-k8 job for arm platform. It will be triggerd by
container4nfv jobs.
Add 2 arm pods to functest-daily pod list.
Change-Id: If8209574263b863f2a907cd962f9511cc3db74ea
Signed-off-by: Jingzhao Ni <jingzhao.ni@arm.com>
|
|
It simply adds OpenStack jobs in OPNFV daily gates.
OPNFV Installers seem good enough to meet the OpenStack merge criteria.
Rally is still excluded as it ends after 3 hours.
Change-Id: I16ea72c1ca49f485d81f9b06b435e9731b56083a
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|