Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Adds jobs for building the following LaaS containers:
- opnfv/pharos-tools-laas-dashboard
- opnfv/pharos-tools-laas-celery
- opnfv/pharos-tools-laas-mq
Having these containers built seperately from docker-compose decouples
the build and deployment phases for the dashboard.
Change-Id: I919066f5defd02fe1bbf96cfdf8ec2a6b3d8757d
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: Idea9af88bd02f647addec9142e0384dc6cf2029a
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
|
|
This is still far from a clean and secure approach, as `pip install`
should not be ran with `sudo`.
However, `-H` limits the area we touch and also fixes some incompat
between disto-provided pip and pip-provided pip.
Change-Id: I0e19dfeaf66f6f453e3868c71016305ae050f0c8
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I450bbd4a3c0e386f949b3b06fe85e74661e2ef2b
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
The current impl doesn't exit as expected when running both tiers and
testcases [1][2].
[1] https://build.opnfv.org/ci/view/functest/job/functest-apex-baremetal-daily-master/324/console
[2] https://build.opnfv.org/ci/view/functest/job/functest-apex-baremetal-daily-fraser/284/console
Change-Id: I934c3f54313522011ed87ebebe77fbb285b8ab49
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
With the rework of Fuel & Armband repos, the condition for using sudo
got mixed up and alternated between on/off for armband's deploy/verify
jobs. Rewrite it based on lab allocation instead of project.
Change-Id: I428c585142017b170233858ec3160fdaf998db0c
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
==~ and its negative form previously used mean the pattern should
match the whole string, while =~ returns true for partial matches.
Change-Id: Ibdeacb4bc221820175b15a87db343fc950e0f9e8
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
While at it, tweak regex for verify job to match 'recheck' right
before EOF.
Change-Id: I3e8e1eeaf2ca947425fa2443b29e150c808eea07
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
- disable functest smoke on arm-virtual* PODs, since we don't perform
a full deployment on those PODs, only a basic integrity check;
Change-Id: I0bcd6da32118ea256652dc74977ef0ee7f2525ab
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Duplicate fuel-verify jobs based on cluster type (virtual, baremetal)
and allow (re)checking changes using a specific scenario:
- ALL changes will trigger a virtual POD CI cycle (build, deploy,
smoke) on submit, rebase etc., just like they used to;
- change comments containing a substring formatted like:
* `recheck: os-odl-nofeature-ha`
* `reverify: os-odl-nofeature-noha`
* `recheck`
will trigger only virtual or baremetal deployments of the required
scenario (default os-nosdn-nofeature-noha) on:
* virtual PODs if scenario is NOHA;
* baremetal PODs if scenario is HA;
- limit arm64 verify job running on arm-virtual2 to the installation
of infrastructure VMs and skip cluster setup to prevent POD time
starvation;
Limitations:
- HA scenarios can only be verified on manual request via a change
comment (e.g. 'recheck: os-odl-ovs-ha');
JIRA: FUEL-390
Change-Id: I6368cfd045180d6a7202b8d817b17a4b123ba2af
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
It is necessary to log the eventBody to console before we attempt
to publish it since it is not possible to see the event body in
case if the publisher errors out due to invalid JSON.
Change-Id: I79cb93f64f5e6e275e306b375210f5f2ed7bd53d
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
|
|
Change-Id: I9bdcbf24573bb2202e8ec3c43b3cdfc2ba7df321
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: Ic54f6fe21dc0e9d2b3a9a2f3db1ba82f08446b6c
Signed-off-by: xudan <xudan16@huawei.com>
|
|
* changes:
[armband] verify: Simplify and move to build hosts
[fuel] Retire Danube stream
[fuel] cleanup: remove unused scenarios
[fuel] cleanup: remove unused job defs & scripts
|
|
|
|
Now that Fuel verify jobs cover arm64 deployments by default, we
only need to validate that the Armband patches still apply on top
of the latest Fuel@OPNFV git submodule HEAD.
While at it, tweak timed trigger order.
JIRA: ARMBAND-401
Change-Id: I4ed20b52906848efff6bad641852d3dd1bee3db3
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Iee41f1fcaf80f0a0b3a58cd189a04cefcbfbb028
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
lf-build2 seems not to have right ports open, causing problems while
connecting to ActiveMQ Message Broker.
https://build.opnfv.org/ci/view/OpenCI/job/openci-opnfv-k8-nosdn-onap-ha-compose-daily-master/10/console
Change-Id: If78cb8b2748080641db851182860f6a8630a323d
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
Change-Id: I52d4ecb5f305f190a9e06c13407fd0927bc45a29
Signed-off-by: Yolanda Robla <yroblamo@redhat.com>
|
|
Change-Id: I9da4c2587874a7ea4ca0f2b90dd7ec15c9e05e34
Signed-off-by: Yolanda Robla <yroblamo@redhat.com>
|
|
Also remove the jms publisher, this is not going
to be used now, as the openci_publisher will be
used instead.
Change-Id: I9a3f4557724cc41ac85ce68a6d0c46ae78864b88
Signed-off-by: Yolanda Robla Mota <yroblamo@redhat.com>
|
|
Change-Id: Ie25586d8ef73a34b68fdf5580df27e5e609e84ce
Signed-off-by: Yolanda Robla <yroblamo@redhat.com>
|
|
|
|
Change-Id: I0d6b8525cc12bb71852a8aeeb67cbc37d0456bcb
Signed-off-by: Yolanda Robla <yroblamo@redhat.com>
|
|
|
|
Force workspace cleanup
Do not use credentials plugin, but hardcode it.
Change-Id: I5b6e59382c25fc75a748f90fbd030521dac9071f
Signed-off-by: Yolanda Robla <yroblamo@redhat.com>
|
|
|
|
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>
|
|
|