summaryrefslogtreecommitdiffstats
path: root/jjb/fuel/fuel-verify-jobs.yaml
AgeCommit message (Collapse)AuthorFilesLines
2019-02-11[fuel, armband] Disable Gambia jobsAlexandru Avadanii1-1/+1
Change-Id: I10df633c478e3bbd2d229dbb4e5cf26d7d9cb82a Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2019-01-11Merge "[fuel] Run functest hunter against master branch"Alexandru Avadanii1-0/+3
2019-01-10[fuel] Run functest hunter against master branchCristina Pauna1-0/+3
Fuel has upgraded to OpenStack Rocky on master branch, so in order to be in sync with the same version of OpenStack in functest, the container with hunter tag must be ran for fuel master jobs. Change-Id: I91d7e209847cd74e6f16ff5c9881f1098911e9d9 Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
2019-01-09[fuel, armband] Disable aarch64 verify jobsAlexandru Avadanii1-3/+1
Our hardware does not support nested virtualization on aarch64, so our verify jobs cannot run any real tests that require spawning VMs on a virtual POD, where all verify jobs were previously scheduled. So all aarch64 verify jobs used to be limited to checking that the Armband patches apply cleanly on top of OPNFV Fuel. Now that all Armband patches are upstream in OPNFV Fuel, the verify jobs became more or less a no-op, so let's just disable them. Change-Id: Ibe86f58978c961e221c90ccb8b2666598981f464 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-10-12Update jenkins-job-builder to 2.2.1Aric Gardner1-2/+2
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>
2018-09-26[fuel, armband] Switch CI jobs to gambiaAlexandru Avadanii1-1/+1
- 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>
2018-09-21[fuel] verify: Use regex find instead of matchAlexandru Avadanii1-1/+1
==~ 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>
2018-09-21[fuel] verify: pass env vars with sudo -EAlexandru Avadanii1-2/+2
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>
2018-09-21[fuel] verify: Enable voting for arm64 deployAlexandru Avadanii1-5/+1
- 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>
2018-09-21[fuel] verify: Add baremetal testing on requestAlexandru Avadanii1-29/+57
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>
2018-09-12[fuel] verify: Align build/deploy docker img tagsAlexandru Avadanii1-1/+1
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>
2018-09-12[fuel] verify: Fix project, branch undef refsAlexandru Avadanii1-1/+3
Change-Id: I6b641c87e2672a9e879865baebfa3a58129823f7 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-09-10[fuel] verify: Multiarch, docker build stepAlexandru Avadanii1-39/+88
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>
2018-07-27[fuel] Remove vping_ssh testcaseMichael Polenchuk1-13/+0
Now healthcheck includes vping_ssh, so remove it as a dedicated test for verifying patches on gerrit to avoid double checking. Change-Id: I4daec677e7d1fdc65997f7a9ab580d5f93ece8a8 Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
2018-06-29[fuel, armband] verify: Use same node for deployAlexandru Avadanii1-1/+1
JIRA: FUEL-375 Change-Id: I01f17a28fdb1bd692d1997b0a32be66de8856a8b Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-05-16Rename files under jjb from 'yml' to 'yaml'Trevor Bramwell1-0/+208
global-jjb only supports the .yaml file ending for jjb jobs. Instead of waiting for a release we're going to rename the files. Change-Id: Icf3339eacd2320c583333e02250998cf6b1881f7 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>