summaryrefslogtreecommitdiffstats
path: root/jjb/functest/functest-ci-jobs.yml
AgeCommit message (Collapse)AuthorFilesLines
2017-03-02functest: Create functest-weekly prototype jobsFatih Degirmenci1-401/+0
Fuel weekly jobs are created, calling fuel-deploy and functest weekly jobs. Experimental scripts have also been removed. Change-Id: If492443e26248731df35e6b6cb5239fb2ae9a86a Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2017-03-02Fix the wrong pod and job name of DaisyJulien1-2/+2
Change-Id: Ic6fea2c189de30875968b436db9469bfb5e9b051 Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2017-02-28Add odl_netvirt as a suite choice for FUNCTEST_SUITE_NAME paramJamo Luhrsen1-0/+1
Change-Id: I86790035c0bb203e8e84c40c863b0750658d6901 Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>
2017-02-24Merge "Add scenarios jobs"Serena Feng1-0/+9
2017-02-22Add scenarios jobsJulien1-0/+9
deployment and integration with functest Change-Id: Ic9f72f4f6bf4d526b51b3254cfc2efd5842dd58c Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2017-02-21[Functest] Refactor Functest-suite jobjose.lausuch1-2/+0
- Remove if clauses for old releases (not used any more) - Use python call to run_tests.py instead of CLI This will allow us to return the proper value to the job. The CLI command returns always 0. - Remove push logs to artifacts Functest-suite is not meant for daily CI runs Change-Id: I34d99cbe5af07a1fcf583a9a0b6ac6ab286c9adc Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2017-02-10Use the aarch64 image for functestCristina Pauna1-1/+1
An aarch64 image was created for functest in https://gerrit.opnfv.org/gerrit/#/c/27801/ This image is build and pushed with https://gerrit.opnfv.org/gerrit/#/c/28291/ In this commit, the aarch64 image is pulled when an aarch64 jenkins slave is used for running functest. JIRA: ARMBAND-180 Change-Id: Idfe7115275a056ef5137cff0a963910c2707457c Signed-off-by: Cristina Pauna <cristina.pauna@enea.com>
2017-02-10Move the compass centos job to intel-pod8wutianwei1-2/+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-07[Functest] Add push-logs to functest-suite jobjose.lausuch1-0/+2
Functest suite is used now by different projects for verify jobs for example. Some of these jobs would like to have the logs in artifacts for further troubleshooting. Change-Id: I2e0c2d9539c2e195a5c4fb6c4708d82e512adf94 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2017-02-01merge GIT_BRANCH and GERRIT_BRANCH into BRANCHRyota MIBU1-1/+0
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-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 Degirmenci1-22/+22
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-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 MIBU1-4/+1
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-143rd party ci: Create functest jobs for netvirtFatih Degirmenci1-0/+5
This is probably not the best way to fix this and will hopefully be aligned with the rest. Change-Id: I0a7602c34c3b5941f36ae0073e7abfdf4b4a9cb4 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-12-12Functest: don't clean existing Docker imagesjose.lausuch1-1/+1
This will save some time. The "docker pull" command takes care of upgrading the image if it exists. Change-Id: I195e0ddac3673cdafb13ab6d78874367420e37ff Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-12-07functest,doctor: CLEAN_DOCKER_IMAGESRyota MIBU1-0/+4
The builder/script 'functest-cleanup' will delete docker images for functest, so that we can make sure the latest functest will be used during the tests. But, it also makes a pod downloads image every time CI triggered functest-suite. This patch adds option 'CLEAN_DOCKER_IMAGES' (default=true), so that the job owner can choose whether he/she wants to drop the docker images or not depends on frequency or charactaristics of the job. Change-Id: I0b7affccb404fb8c4f0939b00d65e363ec62f7c3 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2016-12-01Functest jjob: add the option to provide the rc file as parameterjose.lausuch1-1/+5
Change-Id: Icb5dd3f0f46eb4891609d1f0e4d868e84fe49a14 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-10-18Set arm-pod-3 as non-ci PODcristinapauna1-0/+8
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-4/+0
Change-Id: I8b8cf515d47e6117bfa5804c15fac22ac8b8d90a Signed-off-by: meimei <meimei@huawei.com>
2016-09-19add 'ool-virtual1' into functest pod listRyota MIBU1-0/+5
This entry will be used by doctor's verify job which will triggered by each patch upload into gerrit. Change-Id: I1f4bc8cbb56baf8192ba9d26dcfb80de8cade560 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.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-13[compass] use new pod to run compass jobsmeimei1-0/+4
Change-Id: I9c6ee092cea755aea58a91a696cb338e1eb5df8b Signed-off-by: meimei <meimei@huawei.com>
2016-09-09add doctor-functest verify jobRyota MIBU1-0/+4
This patch adds a new jenkins job which will be executed every time doctor patch is uploaded. The code will be verified by executing doctor scenario on the specific pod using functest. JIRA: DOCTOR-70 Change-Id: I480cd905991ccb1ef7426187fe83cbf1ae798ce9 Signed-off-by: Ryota MIBU <r-mibu@cq.jp.nec.com>
2016-09-07armband: functest jobs refactored to use labelsPaul Vaduva1-3/+20
Change-Id: I50c47a40f3337e7140740f49b09f3e508eb0087c Signed-off-by: Paul Vaduva <Paul.Vaduva@enea.com>
2016-09-02[Functest] Remove exit value job from functest-suite builderjose.lausuch1-1/+0
Change-Id: I8309c027a871246623c199447dcb667b5bb2f066 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-09-01Merge "fuel: Enable triggers of Colorado on zte-pod1 and zte-pod3"Fatih Degirmenci1-0/+8
2016-09-01fuel: Enable triggers of Colorado on zte-pod1 and zte-pod3wu.zhihui1-0/+8
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-31[Functest] Push logs to artifacts regardless if loop failsjose.lausuch1-0/+9
This prevents from exiting the job without pushing the logs to artifacts if the functest loop fails. JIRA: FUNCTEST-443 Change-Id: I6925b5855326df809dbce9f389b10be8a00cf8de Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-08-24Apex, Functest: Adds apex colorado functest jobsTim Rozet1-0/+8
Change-Id: I07d7f0a3cdef3ebe1dec07156791f181a149ba19 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-08-23fuel: Create jobs for ColoradoFatih Degirmenci1-9/+9
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-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/+2
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-14Add zte-pod2 CI jobsJulien1-0/+4
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/+4
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-12add test suite Parser to Functest CI jobSerenaFeng1-0/+1
JIRA: FUNCTEST-412 Change-Id: Ic23f5629e00d4adec62f6021bfd859f439e12825 Signed-off-by: SerenaFeng <feng.xiaowei@zte.com.cn>
2016-07-26[Functest] Increase daily job timeout to 180jose.lausuch1-1/+1
Some installer/scenarios take too long to execute the tests and the job times out.. Although this is not the best solution, we can let the installer teams run the tests to see why it takes too long sometimes) Change-Id: I37cc393c65408741c5f0ecb9cc12ad6297c31d6d Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-07-22functest: Adjust job timeout based on the loopFatih Degirmenci1-4/+7
Change-Id: I405bcbf26965a5290fb8dad9786881251e6aea81 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-07-20[multisite] add new testsuite of multisitemeimei1-0/+1
Change-Id: If63cca009f539125ce877fa05f40178bb1c71247 Signed-off-by: meimei <meimei@huawei.com>
2016-07-08Cleanup slave parametersFatih Degirmenci1-7/+0
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-01Add weekly loop in Functest CIMorgan Richomme1-10/+35
Change-Id: I2d1dfc4c9c09199d2ced56ce47f3376eb8ea8f81 Signed-off-by: Morgan Richomme <morgan.richomme@orange.com>
2016-07-01functest: Set build description to node name for easy identificationFatih Degirmenci1-0/+2
Change-Id: I4e2bdd499d60c07230d5f6a15a2c9fd9a9c8efdd 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-21Functest, Add healhcheck as functest-suite-parameterjose.lausuch1-0/+1
Change-Id: I2212c4e52b6ac7df017b6fda17df2b3a0e4a9406 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-06-16Revert "Apex,Functest: Add healthcheck for Apex verify jobs"Tim Rozet1-1/+0
This reverts commit ca27977f61fe104a5252cdc40b42c6c774724530. Change-Id: I7eedfab682fc9f46c128c4164983ad9ae625b384 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-06-15Apex,Functest: Add healthcheck for Apex verify jobsjose.lausuch1-0/+1
JIRA: APEX-122 Change-Id: I61e04f8e65fe7c35350cd5ab6d5190ffa9ed311f Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com> Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-05-30Functest, switch CI_DEBUG to false.jose.lausuch1-1/+1
JIRA: FUNCTEST-275 At least until we fix the issue with the python logger showing the output twice. Change-Id: I121b6164cd9dc263b0c6f87afb661f853bcca708 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-05-29Apex, Functest: Reconfigure Apex with labelsTim Rozet1-9/+4
Change-Id: Ia56ceefe5bf93cf15f89133c40f0e23c678e11d3 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-05-26compass: Switch using labels instead of slavesFatih Degirmenci1-21/+17
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>