summaryrefslogtreecommitdiffstats
path: root/jjb/functest/functest-ci-jobs.yml
AgeCommit message (Collapse)AuthorFilesLines
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>
2016-05-26joid: Switch using labels instead of slavesFatih Degirmenci1-16/+19
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-41/+70
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>
2016-05-25Enable opencontrail ci jobs in compassmeimei1-0/+3
JIRA: COMPASS-393 Change-Id: Ib079cb543f7ed9ae932ea3af99a8c3f187dd0cbc Signed-off-by: meimei <meimei@huawei.com>
2016-05-24bugfix: Switch to include-raw so curly brackets are not escapedFatih Degirmenci1-5/+5
Change-Id: I22bdffac5888656ee95c458d42c0f6621c822f7f Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-05-24functest: Take builders out of jjbFatih Degirmenci1-120/+9
Change-Id: I546b1b323db2d1839335a34e8293b27f368b0626 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-05-21Rename LF Jenkins slaves and update impacted jobsFatih Degirmenci1-3/+3
Change-Id: If58c84e6f431db88eed3376e446479826da71502 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-05-20Rename Huawei Jenkins slavesFatih Degirmenci1-2/+2
Slave names will be as below. - huawei-us-deploy-bare-1 -> huawei-pod1 - huawei-us-deploy-bare-2 -> huawei-pod2 - huawei-sh-test-2-defaults -> huawei-pod3 - huawei-sh-pod6 -> huawei-pod4 - huawei-us-deploy-vm-1 -> huawei-virtual1 - huawei-us-deploy-vm-2 -> huawei-virtual2 - huawei-us-deploy-vm-3 -> huawei-virtual3 - huawei-us-deploy-vm-4 -> huawei-virtual4 huawei-sh-pod4 will be removed from Jenkins. Please note that this change will result in removal of existing jobs. This is not that crucial since the use of labels will result in same. Change-Id: I63798c799a402b1694ee0767ffdb45a597897cd9 Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-05-18Functest, create builder for test suitejose.lausuch1-2/+11
Change-Id: Ib01658ed1e8c85b6408d32a1b367702bc6b32abd Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-05-12Rename Orange Jenkins SlavesFatih Degirmenci1-1/+1
orange-test1 -> orange-pod5 orange-fr-pod2 -> orange-pod2 Change-Id: Id5a31db98d349bef654fb59ab03e52e6cc50611f Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.com>
2016-05-12Add functest for main branch fuel installer on zte-pod1zhifeng.jiang1-0/+3
JIRA:RELENG-87 Change-Id: I4ca1ea6a206fcadc94f813e33bae4751236ee24d Signed-off-by: zhifeng.jiang <jiang.zhifeng@zte.com.cn>
2016-05-06Functest, redirect to /dev/null the output of some docker commandsjose.lausuch1-3/+2
That output is irrelevant and doesn't help to debug anything, and it is very extensive. Change-Id: If97ff388d5ab53c67d7cd5c5e6f2fff1f202e6a4 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-05-02Functest: add support to pass custom parameters to dockerCiprian Barbu1-1/+3
This makes it possible to pass extra environments or volumes to docker by listing them in a file at ${HOME}/opnfv/functest/custom/params_${DOCKER_TAG}. This way different parameter (env vars and volumes) can be specified for stable and master. Change-Id: I010fae9802dd413f0ca6ae9fb3ef0f03b81db3c2 Signed-off-by: Ciprian Barbu <ciprian.barbu@enea.com>
2016-05-02Merge "Fuel: add functest for brahmaputra on arm-pod1"Fatih Degirmenci1-0/+3