Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I4cecaf7302fa1f39aa1e8b2c3e34f11ee49b4359
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Global JJB now has non-JJB YAML configuration and requires action on the
ci-management repo when upgrading to this version of Global JJB to
prevent JJB from picking up these YAMLs as config. Follow the
instructions below BEFORE upgrading globall-jjb:
cd <git-root>
git mv jjb/global-jjb global-jjb
mkdir jjb/global-jjb
ln -s ../../global-jjb/shell jjb/global-jjb/shell
ln -s ../../global-jjb/jjb jjb/global-jjb/jjb
git add jjb/global-jjb
git commit -sm "Prepare repo for global-jjb v0.25.0"
Git diff confirms no changes.
diff -bur . /tmp/releng/job_output/
Change-Id: I6d7239b8bab8ef08368f833d9a64cd94a824b158
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
From the release notes:
Upgrade to global-jjb v0.24.6 before performing this upgrade. This
ensures that jjb-verify job pulls in a regex fix that will allow it to
verify the v0.25.0 upgrade.
Change-Id: I48335de599b46b7e6c70f8bb77fb8c254cfe85f4
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
|
|
|
|
Change-Id: I89040a4f7ac493efe8a11a268ce891c156e53c18
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
|
|
jjb/lf-ci-jobs.yaml has jjb-version: 2.2.1 as a minimum
change block-level to blocking-level:
https://review.openstack.org/#/c/608092/
We will need to change this back once we move past
jenkins-job-builder>2.5.0
Change-Id: I12d0f55ee3c2dad20340ebf0fa8428ee1ad8484c
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
Change-Id: I388d5b46d206655990f3fb2723a90e8ed4397c89
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
|
|
Push OPNFV docker builds for clover-ns-modsecurity-crs image
Change-Id: I134108d78d84de8a04bb7372c49314d0491a1248
Signed-off-by: JingLu5 <lvjing5@huawei.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Adds the gambia stable branch stream.
Change-Id: Ic1afb65b580396f11c00488a7f135e0e5cdc96cd
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
|
|
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: I7baab0712ee5531b12ac15af5c36672778a8c6d4
Signed-off-by: Qiaowei Ren <qiaowei.ren@intel.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>
|
|
|
|
Change-Id: I7841a2397e3c856726e44da0bb4281e442b69192
Signed-off-by: Stephen Wong <stephen.kf.wong@gmail.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>
|
|
|
|
|
|
|
|
Change-Id: Icc8c518bda5240d814be9110b5d09b19c5868078
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
Change-Id: Iaf668d3f496f7a5343e10e59ff2b7f9073c52f28
Signed-off-by: dimitris.tsiolakis <dmts@intracom-telecom.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>
|