Age | Commit message (Collapse) | Author | Files | Lines |
|
This node has permissions for Google Storage to upload the archive while
master does not.
Also adds myself to list of recipients so I'll get notified when the job
fails.
Change-Id: I07a13dcc72c59854222f6e5ace9d1e18c24e6479
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
The dockerfile path is relative to the dockerdir, not the root of the
cloned repository.
Change-Id: I7836abf8f15d4d9f14cb8d39bc951ec9341d39ba
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
Removing the cperf docker image in clean just adds more overhead to the
next cperf run, because the entire docker image has to be re-downloaded.
Docker pull will automatically download the difference between the old
image and the new image (less bandwidth) so there is no reason to remove
the image.
Change-Id: I79ba2af20e3bdacfedc28d468fb629e040d7098f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I0f5f8225c38f535241ecd78aa93aee28782cbc4f
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
Change-Id: I71a3ed0c242554cc685f4a610c3651d1e2cab98f
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
|
|
Now that we branched for Gambia, we want Gambia code to handle promotion
for Queens snapshots, while Apex master is responsible for rocky/master
promotions.
Change-Id: I6f4fffabd728d72fe9b6b2e5a983f6d8762272a9
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
The path to reach the inventory was wrong and thus the error message in
CI:
Unable to parse /root/releng-xci/.cache/repos/openstack-
ansible/inventory/dynamic_inventory.py as an inventory source
Change-Id: Ic9e01e0895f3df2f6f27d782b8375dbcceb036e6
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
The logic should have been checking for stable/fraser and didn't account
for newer branches other than master.
Change-Id: I1164ce57338ba1734aa68c98bfe22a8a5f4209ac
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
Set IMAGE_PROPERTIES and FLAVOR_EXTRA_SPECS environment variables
for functest CI run for ovs and fdio scenarios.
Change-Id: Ib2be311ee28d4ae633ec5496a12e741f701cc7ab
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
Change-Id: I0e9521a4b5dcb025464b6b193848454aacd5a86c
Signed-off-by: wutianwei <wutianwei1@huawei.com>
|
|
Fix docker error because of environment variable IMAGE_PROPERTIES
for fuel installer in functest
Change-Id: I916f965f8432216104b767e5aa62dc93a8f6ce72
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
Change-Id: Iebab0714f1cd7123c18d98a41b7da224726c5421
Signed-off-by: xudan <xudan16@huawei.com>
|
|
|
|
With using scsi volume device type, additional image
extra_properties are needed.
Set environment variable IMAGE_PROPERTIES when installer is fuel for
functest test run.
Related to:
https://gerrit.opnfv.org/gerrit/#/c/61913/
https://gerrit.opnfv.org/gerrit/#/c/63225/
Change-Id: If35aa282abaf5dab1a5bacc2f26fe89292b09605
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
Updates the docker builds for LaaS to share the same context but point
at different Dockerfiles. This way the dashboard code can be copied into
the container instead of requiring to be volume mounted.
Change-Id: I26fe345c8901b772a2e9da56fac71956a8a76583
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
To pass functest healthcheck test in odl scenarios, some odl variables
must be fetched. To do so, we require to know where opendaylight is
deployed and that we can know using the dynamic_inventory.py file in OSA
This is needed for this patch:
https://gerrit.opnfv.org/gerrit/#/c/63175/
Change-Id: I04643ce93078bad53838e4d4e611f7684d4bd314
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
|
|
* changes:
Enable yardstick-docker-build-arm-push-gambia job
Make Gambia stream available to ARM Docker builds
Enable yardstick-docker-build-push-gambia job
|
|
Similar to https://gerrit.opnfv.org/gerrit/63177 (done for x86_64).
It replaces the yardstick-docker-build-arm-push-fraser job, for the
same reasons.
Depends on https://gerrit.opnfv.org/gerrit/63179
Change-Id: I482bc05d4c6d1316bfde799a44360decacb60a5e
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
Similar to https://gerrit.opnfv.org/gerrit/63047 (done for x86_64).
Change-Id: Ie61a11c60ce0fd7c724f308ecfdcca982ebdf3ec
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
It replaces the yardstick-docker-build-push-fraser job, because the
logic in jjb/releng/opnfv-docker.sh L106-L119 has limited options for
docker image tags:
- 'latest', for git commits on master branch
- tag-name, for git tags
- 'stable' otherwise, i.e. for git commits on *any* stable branch.
This means we can have only one (stable) job building and pushing
docker images, in order to prevent the 'stable'-tagged image from
switching between fraser and gambia contents, depending on the stable
branch where the most recent change was cherry-picked and committed.
Unfortunately, disabling the yardstick-docker-build-push-fraser job
also means that further git tags on the stable/fraser branch will not
result anymore in building and pushing new docker images with the
intended tag-name and contents.
Change-Id: Ieec1cdc6230e4c000c159cd743c587561c788fc3
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
JIRA: DOVETAIL-742
This patch runs unit tests on gerrit events instead of hello world.
Change-Id: I3c0fd42532871cddab1bf69f84b9ac83fc7a0cf2
Signed-off-by: Stamatis Katsaounis <mokats@intracom-telecom.com>
Depends-On: https://gerrit.opnfv.org/gerrit/63157
|
|
Correct the scenario error in container4nfv for
functest-k8s.
Change-Id: I7a24508ae35c44baa22f1fab8b1a72388dedf0b0
Signed-off-by: Jingzhao Ni <jingzhao.ni@arm.com>
|
|
Change-Id: Icb84e4860021f5aa24de0d68542863da7fee4aff
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
|
|
Change-Id: I58fc2c56d32c04f2c96136ed69335b5c64771e05
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|
|
|
|
|
|
|
|
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>
|