summaryrefslogtreecommitdiffstats
path: root/jjb/yardstick
AgeCommit message (Collapse)AuthorFilesLines
2017-02-25yardstick: email receiver changeMatthewLi1-1/+1
Change-Id: I3cf28afe76bc0cd0bbabae28ad2620a565756e93 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2017-02-10Move the compass centos job to intel-pod8wutianwei1-11/+2
We fixed the issue of accessing database failed on intel-pod8. Some problem happened in Huawei Munich Lab.So we move the CI job to this pod. Change-Id: Iefddcf2bef2cc296b1abd2d224b78c6dbc522295 Signed-off-by: wutianwei <wutianwei1@huawei.com>
2017-02-05yardstick: install python3-dev so we can build librariesRoss Brattain1-0/+2
We need python3-dev so we can install Python3 libraries like lxml Otherwise we fail with: building 'lxml.etree' extension creating build/temp.linux-x86_64-3.5 creating build/temp.linux-x86_64-3.5/src creating build/temp.linux-x86_64-3.5/src/lxml x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -g -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/libxml2 -Isrc/lxml/includes -I/usr/include/python3.5m -I/home/jenkins/opnfv/slave_root/workspace/yardstick-verify-master/.tox/py3/include/python3.5m -c src/lxml/lxml.etree.c -o build/temp.linux-x86_64-3.5/src/lxml/lxml.etree.o -w src/lxml/lxml.etree.c:85:20: fatal error: Python.h: No such file or directory compilation terminated. Compile failed: command 'x86_64-linux-gnu-gcc' failed with exit status 1 creating tmp cc -I/usr/include/libxml2 -I/usr/include/libxml2 -c /tmp/xmlXPathInitmtir1fki.c -o tmp/xmlXPathInitmtir1fki.o /tmp/xmlXPathInitmtir1fki.c:2:1: warning: return type defaults to ‘int’ [-Wimplicit-int] main (int argc, char **argv) { ^ cc tmp/xmlXPathInitmtir1fki.o -lxml2 -o a.out error: command 'x86_64-linux-gnu-gcc' failed with exit status 1 JIRA: RELENG-190 Change-Id: Icea4cff9bb9699fbd4bfc25dd201ff8bc6e6a902 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-02-02yardstick: use tox to add support for python3Ross Brattain1-14/+1
We need to start adding support to Python3 to match Openstack support for Python3. Use tox and move all the env setup to tox.ini JIRA: YARDSTICK-452 Change-Id: Ie57b5edd87ab6fad641a174f468d3265757e0f71 Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
2017-02-01merge GIT_BRANCH and GERRIT_BRANCH into BRANCHRyota MIBU3-5/+2
GIT_BRANCH parameter is different; master or stable/danube in daily jobs, but 'refs/changes/57/27657/6' in verify jobs. This breaks some job builders triggered by the both types of jobs. We have GERRIT_BRANCH parameter for verify jobs to identify stream and expected branch into the patch will be merged after it got +2 and submitted. To avoid further confusion and to have common job builders for daily and verify jobs, this patch introduce BRANCH parameter. GERRIT_BRANCH is now deprecated. Change-Id: Ibcd42c1cd8a0be0f330878b21d3011f1ec97043b Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2017-01-26Bugfix: yardstick verify failedJingLu51-0/+1
JIRA: RELENG-187 see log: https://build.opnfv.org/ci/job/yardstick-verify-master/1688/console Change-Id: Id6ac66a34fba5a0d18ab4a60e457582bbb4f03d0 Signed-off-by: JingLu5 <lvjing5@huawei.com>
2017-01-24Bugfix: yardstick verify failedchenjiankun1-1/+1
JIRA: RELENG-187 yardstick verify failed. There is some wrong with setuptools new version 34.0.1 I will change it to 33.1.1 see log: https://build.opnfv.org/ci/job/yardstick-verify-master/1688/console Change-Id: If3c65a9a8047b57549c40501b0a83118cd5dc3e7 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2017-01-20[macro] property logrotateRyota MIBU1-0/+1
This patch defines 'logrotate-default' property and replace 'logrotate' by it, as 'logrotate' is deprecated on jenkins>=1.637 . Change-Id: I900975e5b3f590bb7a4d430e2f623931ae782bf4 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2017-01-09Remove colorado jobs and create danube jobsFatih Degirmenci2-16/+16
Danube stream for the projects with daily jobs is disabled. Danube stream for the projects without daily jobs is left as enabled as there will be no changes coming to danube branch until branch is created. Dovetail, Apex and Fuel jobs have not been updated yet. Change-Id: Ice39826c8f829157fa864370557837290838f634 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-12-30improve yardstick logger to output Debug info to artifactsrexlee87762-1/+15
JIRA: RELENG-158 Change-Id: I3bd91c671fa3dcac5cd47ca12610457fd1ab5a5b Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2016-12-19fix ci jobs (daily && no branch param)Ryota MIBU1-0/+2
Change-Id: Iad856adf625a56c2f5c366fb414746d1e9e16691 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2016-12-19clean scm defenitionsRyota MIBU2-12/+3
This patch makes sure we use 2 types of scm, and allows us to specify them by adding one line in job-templates. - git-scm # for daily jobs and merge jobs - git-scm-gerrit # for verify jobs [New] Change-Id: Iddc8a5e0e115193c7081a6d6c53da209900e95c8 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2016-12-01Restrict Gerrit Triggers to OPNFV Gerrit ServerTrevor Bramwell1-0/+2
With the addition of ODL and OpenStack Gerrit servers, it's important we don't generate additional noise by accidentally building against these Gerrit servers when we don't intend to. JIRA: RELENG-179 Change-Id: Ia163c6c3eaa58e8e21dc6548a839062fcbde39ed Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2016-11-28Make the requirements.txt compatible with Coloradochenjiankun1-1/+1
JIRA: YARDSTICK-428 Now in master, we move the requirements.txt from tests/ci/ to yardstick root path. But in colorado, this has yet to be done.If we cherry pick from master to colorado, it will encounter error. So we must make it compatible. Change-Id: I0537d989e677b73e19a1e093166493f3f6d25783 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-11-18Modify yardstick requirements.txt path config in relengchenjiankun1-1/+1
JIRA: YARDSTICK-415 Change-Id: I8e3e38842e10e5fbc335f3f23250f0292f2c05c5 Signed-off-by: chenjiankun <chenjiankun1@huawei.com>
2016-10-25[Yardstick] Add default DB_BACKEND for virtual podJingLu51-8/+8
JIRA: YARDSTICK-357 Change-Id: I5a6e77366733e1a871c8f1574d15996456ec080d Signed-off-by: JingLu5 <lvjing5@huawei.com>
2016-10-18Set arm-pod-3 as non-ci PODcristinapauna1-0/+18
arm-pod-3 will be removed as CI pod and this commit add triggers to make it a non-ci pod Change-Id: Ice16b8d32c553a059a2c9885fd801a736a59a14d Signed-off-by: cristinapauna <cristina.pauna@enea.com>
2016-10-09[compass] put huawei-pod2 into CI resource poolmeimei1-13/+0
Change-Id: I8b8cf515d47e6117bfa5804c15fac22ac8b8d90a Signed-off-by: meimei <meimei@huawei.com>
2016-09-18[bugfix] use huawei-pod2 to verify coloradomeimei1-1/+1
Change-Id: I9e402d395a3c90f65d0e73f9ef18c08e0801afad Signed-off-by: meimei <meimei@huawei.com>
2016-09-18Merge "[compass] use new pod to run compass jobs"Jun Li1-0/+13
2016-09-13[compass] use new pod to run compass jobsmeimei1-0/+13
Change-Id: I9c6ee092cea755aea58a91a696cb338e1eb5df8b Signed-off-by: meimei <meimei@huawei.com>
2016-09-13yardstick: enable colorado branch for arm-pod2Paul Vaduva1-0/+5
Change-Id: I4756b64d302c2e44b0cb84d0ad4e34288eae25fa Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
2016-09-02yardstick: updated yardstick jobs for armband to use labelsPaul Vaduva1-2/+37
Change-Id: I38aac6caf4f439e6524bf08e5dd038bca01180cf Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
2016-09-01fuel: Enable triggers of Colorado on zte-pod1 and zte-pod3wu.zhihui1-0/+10
Enable triggers of Colorado on zte-pod1 and zte-pod3. Meanwhile, add colorado branch for zte-pod1 and zte-pod3 in Functest and Yardstick. Change-Id: I575d37356c9223935d5975a834589b33f9e7498b Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
2016-08-24yardstick: Pull the right image for master and colorado branchesFatih Degirmenci1-2/+3
Change-Id: I868b837f67d24c53ee40bbd03fb1997da4938b3b Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-08-24BugFix: Fix a wrong commentJingLu51-1/+1
Change-Id: Ic5c9d35ccc92d8f19419c9b25476c0e084c7299f Signed-off-by: JingLu5 <lvjing5@huawei.com>
2016-08-24yardstick: Pull image with stable tagFatih Degirmenci1-1/+1
Change-Id: I47cb8e3ff448b8adc26b62201b15ddd3476dd0c1 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-08-23Merge "Create project jobs for colorado branch"Ryota Mibu1-1/+7
2016-08-23fuel: Create jobs for ColoradoFatih Degirmenci1-10/+10
This change contains updates that impact compass and joid jobs due to updates in functest and yardstick that remove brahmaputra branch. Please note that the triggers for colorado haven't been created yet. It will be done once the basics in place. Change-Id: Id5eb8c406d34ff9f3ac59f73243034cbf49b23f0 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-08-22Create project jobs for colorado branchFatih Degirmenci1-1/+7
Daily jobs for Colorado branch for installer and test projects have not been created yet and it needs to be done via separate patches. Change-Id: I34517e89dfc502ce5741733e01bf8425d513df02 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-08-19Merge "[ZTE PODS]override fuel ip in functest and yardstick ci job"Fatih Degirmenci1-1/+1
2016-08-19joid: Create jobs for orange-pod1 and remove brahmaputra jobsFatih Degirmenci1-2/+10
Change-Id: I61b68a7db60193f5525de7151e43b7752e5dd604 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-08-19[ZTE PODS]override fuel ip in functest and yardstick ci jobwu.zhihui1-1/+1
For all zte pods, the fuel ip is not 10.20.0.2 . It need to override. Change-Id: Ib9533c28d9d03fdfc4804955de9eee7501453cd9 Signed-off-by: wu.zhihui <wu.zhihui1@zte.com.cn>
2016-08-18arm-pod1: Adding arm-pod1 to yardstick ci jobsPaul Vaduva1-0/+13
Change-Id: I00ea21566bd2244c35bdf658eb95e8cf435b7be9 Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
2016-08-14Add zte-pod2 CI jobsJulien1-0/+13
1. CI scenario: os-odl_l2-nofeature-ha using Fuel installer 2. Adjust qtip daily job from zte-pod1 to zte-pod2 Change-Id: I3e4e1adf3a6865a4cc9be81522472c781a8aea4f Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2016-08-13Add zte-pod3 in yardstick and functest jjbJulien1-0/+5
Deployment in zte-pod3 successfully but yardstick and fucntest can not be triggered. JIRA: PHAROS-247 Change-Id: I5407f8c51bac83263b9f165558a38fa0db199868 Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2016-08-11Fix Yardstick connection issue on virtual envMichal Skalski1-0/+5
Libvirt creates iptables rules for NAT network which reject inbound connections which not originate from host. Use the same appraoch as for functest and add iptables rule which allow connections from yardstick container to libvirt vm. JIRA: FUEL-166 Change-Id: I43840bd15cb3ff3fc0f8306ff43c83aabfa9b06f Signed-off-by: Michal Skalski <mskalski@mirantis.com>
2016-08-09Add ZTE-POD3 in CIJulien1-0/+8
Add ZTE-POD3 to support whole procedure of CI, including: deployment, yardstick and funectest. Currently it supports os-nosdn-kvm-ha scenario at the initial step JIRA: PHAROS-247 Change-Id: I70dde8765696ee08339e7cada2428f8461b5f3a2 Signed-off-by: Julien-zte <zhang.jun3g@zte.com.cn>
2016-07-25clean opnfv/opnfv-docs.ymlRyota MIBU1-14/+0
- make 'opnfv-docs-*' jobs run against all repositories which has docs directory. - remove docs builder from yardstick-project-jobs JIRA: RELENG-133 Change-Id: Id0cf6e600ed112c6f082f6bc924eaeccb0481e49 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2016-07-18change ci from base-on-pod to base-on-scenario (in progress)rexlee87762-4/+4
1. first need to change in yardstick 2. then change in releng to modify the input parameter JIRA: YARDSTICK-299 Change-Id: Ie9c96d4ddc6b15b0488ef1cff1f2c7531429baf0 Signed-off-by: rexlee8776 <limingjiang@huawei.com>
2016-07-14Merge "fixes for docs-build.sh migration"Aric Gardner1-2/+2
2016-07-08Cleanup slave parametersFatih Degirmenci2-10/+2
This is the first step towards having alignment of the job structure, applying commit gating and use of labels for all installer jobs. Apart from the above, it also - puts all CI baremetal and virtual PODs together - gets rid of use of slaves directly for CI baremetal and virtual PODs - switches labels for all CI baremetal and virtual PODs using below labels {installer}-baremetal {installer}-virtual - puts all CI build slaves together and switches to labels - except huawei-build - puts all none-CI PODs together Please note that this change does not impact the overall job structure. Change-Id: I2d8d15799a57fe7e063d39f81b96d19c218b100e Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-07-07fixes for docs-build.sh migrationRyota MIBU1-2/+2
JIRA: RELENG-130 See also https://gerrit.opnfv.org/gerrit/16515 . Change-Id: I365ecc4efd6f361f76ec527b4b43fae643f8478b Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2016-07-01Set build description to node name for easy identificationFatih Degirmenci1-0/+2
Change-Id: Iaa1b15badf9750f47a68612f4dae48952de3a3d4 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-06-30Add Project Option to Throttle PropertyTrevor Bramwell1-0/+1
This is a required field for JJB > 1.4 Change-Id: Ifb6f5d4b3a28f2d85f546151ca9aca4a4061f3ef Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2016-06-06Yardstick: rename test suite scriptMatthewLi1-1/+1
JIRA: YARDSTICK-279 two scripts are with the same name run_tests.sh, for unittest and test suite running, confusions are made here, this should be merged after https://gerrit.opnfv.org/gerrit/#/c/14687/ Change-Id: I31aca6144b94a0fd167f5ed77580ba8d9ac4c917 Signed-off-by: MatthewLi <matthew.lijun@huawei.com>
2016-05-30Yardstick, Apex: Fixes yardstick to use right Apex vm name (undercloud)Tim Rozet1-1/+1
Change-Id: I709dbf36667202ed0e1feb4793aa10071dc137c4 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-05-26compass: Switch using labels instead of slavesFatih Degirmenci1-45/+39
This change switches compass jobs to use labels instead of tying jobs to slaves. The changes in detail are: - Compass jobs can roam on any pod that is labelled with compass-baremetal and compass-virtual. - Above means that there is no branch/pod allocation anymore. - New jobs are created in order to get rid of pod names from them and just use baremetal or virtual in names. - Old jobs are removed. - Related test jobs are updated. - huawei-virtual label is renamed to compass-virtual since we still have installer specific slaves, not company specific. In future the job might end up on a none-Huawei slave too. - huawei-pod2 is not a CI POD so it is left in none-CI PODs section. - block relations and triggers might require fine tuning and left to compass project to decide how to adjust Job structure remains same; one parent job calling 3 downstream jobs: deploy, functest, yardstick. The OS to deploy (trusty or centos7) needs to be solved in a separate patch in a sustainable way. Change-Id: I22bfaff36640667b6764f0e303a3286af0eb41b2 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-05-26joid: Switch using labels instead of slavesFatih Degirmenci1-35/+35
This change switches joid jobs to use labels instead of tying jobs to slaves. The changes in detail are: - Joid jobs can roam on any pod that is labelled with joid-baremetal and joid-virtual. - Above means that there is no branch/pod allocation anymore. - New jobs are created in order to get rid of pod names from them and just use baremetal or virtual in names. - Old jobs are removed. - Related test jobs are updated. - POD specific parameters are updated and instead of adding pod specific parameters, they now become parameters for all the pods labelled with same label. It is not a problem at the moment as both Intel PODs (pod5, pod6) have same parameters but a different pod with different parameters will require alignment between pods. Job structure remains same; one parent job calling 3 downstream jobs: deploy, functest, yardstick. Change-Id: I30d270cd05ba3756f6f161d65ee5160eab6b80f4 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-05-25fuel: Switch using labels instead of slavesFatih Degirmenci1-90/+79
This change switches fuel jobs to use labels instead of tying jobs to slaves. The possibilities and changes introduced with this approach are - If things do not work as expected, slave-label parameter can be set to certain slave name to get back to old way of tying jobs to slaves. - If a scenario requires a different slave, it can still be created using baremetal or virtual but the label can be different, pointing to a slave that is capable of running that scenario. (fuel-baremetal-multisite, etc.) - The auto-trigger-name for brahmaputra is moved under the branch anchor and can be used like this if triggers for all all the jobs for a certain branch need not to be triggered automatically but job is still kept enabled in case if some crucial bug needs to be tested. - No of max concurrent builds stepped to 4 in order to use all the labelled slaves available. This will require some adjustments before colorado jobs start to run in order to share resources between branches fairly. - All the fuel CI PODs except lf-pod1 have been removed. Change-Id: I91eca6743bb3d34263e634f9b74550efa1e2ddbe Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>