Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
|
|
|
|
|
|
Add Gambia jobs for Yardstick daily.
Keep fraser jobs until Gambia 7.0.0 is released.
For fraser-tied PODs, use docker image tag 'ovp-2.0.0'.
Change-Id: I6dca72807db1caf9adfc5ce5949c50ad70af5361
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
Add Gambia jobs for Yardstick gate:
- yardstick-verify-gambia
- yardstick-merge-gambia
Keep fraser jobs until Gambia 7.0.0 is released.
Gambia jobs for Yardstick daily will be added in next patch.
Change-Id: Id02bcb8197dd1f6d0b8f5baddef684a97e269a14
Signed-off-by: jenkins-ci <jenkins-opnfv-ci@opnfv.org>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
Signed-off-by: rexlee8776 <limingjiang@huawei.com>
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
|
|
This suite is failing with disconnects for the SSH connection to the
overcloud controller. Disabling it for now until we can figure out what
the problem is. Only happens in this suite:
https://build.opnfv.org/ci/job/cperf-apex-csit-master/104/consoleFull
Change-Id: I15eda3009f181c190bcef6e51b00d22070d9e444
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This adds verify and merge jobs for building and publishing the OVN4NFV
documentation to ReadTheDocs (RTD).
Change-Id: Ifb97b3978150d923ef4728e7423b2c02d44978e4
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Pulling an older version of CSIT had no effect, so reverting that
change. Move L3VPN IPv6 CSIT suite to be first, to rule out a timing
issues along the suites, and determine if the problem with the socket
error is specifically somethign to do with this suite.
Change-Id: If523c6102283d00ae0deb1e96e3f89455be7472a
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
L3VPN IPv6 tests fail consistently. This patch checks out a version of
CSIT right before an update was done to all the L3VPN test. This patch
will be used to validate if the bug was introduced by that commit, and
reverted either way.
Change-Id: I2998cc7cfae183048e5ff1d06fd6bcdf16dd8e41
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Some changes alter the docs yet still don't trigger the verify job
due to the pattern being too restrictive.
Change-Id: I775bfdce5e31a4334d21da10ff3072268b2b6155
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
LaaS is using the upstream rabbitmq container now, so there is no need
for this build.
Change-Id: I08d2dc07eb6cd9cc732b25fd6dee2f342117d857
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: Ied4eb884b9e61a43d21a87f9cf645b89d043d3a6
Signed-off-by: xudan <xudan16@huawei.com>
|
|
Change-Id: Iac803fe18e6c1fcfcefb61dfb7ea03cbed5a51d1
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Includes a minor fix to ipv6 rocky scenario.
Change-Id: I55440dff2fcf7674d4a9c86d9dcb131c226e68ea
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
With the move to upstream artifacts post-fraser the checks to use
upstream artifacts were relying on BRANCH == 'master'. This doesn't
scale as we preserve fraser functionality but add more branches like
gambia. Therefore inversing the logic to accomodate for new branches.
Change-Id: Ice17f6afd33744f44d253d320a194c3f6d02d8bf
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
Adds Gambia daily/verify jobs and prepares to migrate master queens
scenarios to rocky scenarios.
Change-Id: I7bfe6202e00fd62c1e668f3a6f9b481b9fbca99d
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
- keep fraser jobs for Dovetail, schedule 4 CI runs / week / arch;
- stop running Functest/Yardstick for fraser to cut down CI time;
- reschedule master/gambia triggers to ensure an uniform CI POD
allocation across the week;
- enable gambia triggers;
Change-Id: I2a66628ff3525cc9cbd4ffbb4b790633257b6cba
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
Change-Id: I4280286aac855f3fcab5a72aa82e6f8087bbb63e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
|
|
|
|
Change-Id: I432061b472c22dfd65821f8aeaf9c0c5671f3759
Signed-off-by: Sofia Wallin <sofia.wallin@ericsson.com>
|
|
Change-Id: I70f8e7c9372e22e6f3e357b48a0a49f44a4d9078
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Ic1430742e98dd0e98ea3456c636a910c22a90e88
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
Functest job timeout is not enough
Functest jobs are aborted after 480 min
Change-Id: I74dfe12b08e322aad53e10d5808b5b739b8d9ce2
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
The current codebase was intended for Fuel@OPNFV up to and including
the Danube release (based on Fuel@Openstack).
Starting with the Euphrates release, Fuel@OPNFV is based on Mirantis
Cloud Platform (MCP), so the Fuel adapter in modules.opnfv needs a
rework to accomodate the new platform:
- remove unused obsolete code in opnfv.utils;
- switch to key-based SSH auth instead of password-based;
- drop proxy-ing SSH to cluster nodes via installer node, instead
SSH directly via PXE/admin network;
Notes:
- MaaS node (when present) is marked with 'installer' role to prevent
ovs-vsctl queries on it;
- gtw01 node (when present) is not marked with any role yet;
JIRA: FUEL-394
Change-Id: If2b7744b950cd502df8eaca0137c9f845a9d077d
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
|
|
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>
|
|
|
|
|
|
|
|
|
|
|
|
Change-Id: Ic5e0a004422264fb91f27b1d1152518ef7b159b3
Signed-off-by: Martin Klozik <martin.klozik@tieto.com>
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.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>
|
|
Change-Id: I3f3b0b150defb12553740f0d4c3ec111fceb7a5b
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: I135189c6fa8fbf01f67f37547ca120779c08fbc9
Signed-off-by: Manuel Buil <mbuil@suse.com>
|