summaryrefslogtreecommitdiffstats
path: root/jjb/functest
AgeCommit message (Collapse)AuthorFilesLines
2016-11-04Don't run Functest unit tests for Colorado branchjose.lausuch1-1/+1
run_unit_tests.sh is a new thing for Danube, it shouldn't be executed in Colorado verify jobs. Change-Id: Ibc9fd41ae390ef2fcb7d448914dd65a7b9166781 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-10-28Merge "Trigger test unit execution on verify + Published for jenkins"Morgan Richomme1-1/+29
2016-10-19Trigger test unit execution on verify + Published for jenkinsMorgan Richomme1-1/+29
Signed-off-by: Morgan Richomme <morgan.richomme@orange.com> Change-Id: Ieb8e291d31479fff1c7cad941eb9be83cd4b670f Depends-On: Icd958552fafb4e8dc58f9008586bcaf33862ccd4 Signed-off-by: Morgan Richomme <morgan.richomme@orange.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 MIBU2-1/+7
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] Fix typo exiting with a ret_val variablejose.lausuch1-1/+1
Change-Id: I39d085726551ac1db2531d474d9c407840f5ffc0 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-08-31[Functest] Push logs to artifacts regardless if loop failsjose.lausuch3-0/+27
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-23Merge "Create project jobs for colorado branch"Ryota Mibu1-1/+5
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-22Create project jobs for colorado branchFatih Degirmenci1-1/+5
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/+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-25[Functest] Add DEPLOY_TYPE in the container creationjose.lausuch1-1/+4
Change-Id: Id06771db96d1ca014c153ffc2b7567d6b2ea07ea 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-04Merge "Add weekly loop in Functest CI"Morgan Richomme2-10/+35
2016-07-01Apex, Functest: Fixes iptables ruleTim Rozet1-1/+1
Something in Apex is pushing the RETURN rule down the chain, and adding REJECT reject-with icmp-port-unreachable. This enhances the check to make sure not only does the rule exist, but it is at the top of the chain. Change-Id: I527bc45c30008aaf30d5bc9e1d474a14065b3fdf Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-07-01Merge "Functest, Apex: Add iptables forwarding rule"Tim Rozet1-0/+7
2016-07-01Functest, Apex: Add iptables forwarding ruleTim Rozet1-0/+7
Change-Id: Ice55eece4aad6b9b8a1f51ebac13e26251b50708 Signed-off-by: Tim Rozet <trozet@redhat.com>
2016-07-01Add weekly loop in Functest CIMorgan Richomme2-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-21Functest, fix stackrc docker volume for Apex deploymentsjose.lausuch1-2/+2
Change-Id: Iea61baaca6f52fc794011aba40195c76c6da6b68 Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-06-21Apex, Functest: Fixes ssh options when copying Apex stackrcTim Rozet1-1/+2
Change-Id: I53e7e208d380beb2799182dc85394215d7397f7c Signed-off-by: Tim Rozet <trozet@redhat.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-06-15Fixed destintation path used for stackrcLuke Hinds1-1/+1
JIRA: RELENG-116 Change-Id: I6aaa933616c6bb2d31ebcd51fbccaac6ed92aef4 Signed-off-by: Luke Hinds <lukehinds@gmail.com>
2016-06-15Merge "Functest, add stackrc file to container for security tests in Apex"jose.lausuch1-1/+4
2016-06-15Functest, add stackrc file to container for security tests in Apexjose.lausuch1-1/+4
JIRA: RELENG-116 Change-Id: I178bc9046b3dc37b29b1b2fffd5c477ce4971afc Signed-off-by: jose.lausuch <jose.lausuch@ericsson.com>
2016-06-15Tie all verify/merge/build to opnfv-build-ubuntuFatih Degirmenci1-1/+1
We reconfigured centos build server now and it is important to know which jobs require centos and which ones ubuntu. The machines with ubuntu were labelled with opnfv-build previously, preventing us from keeping track of which projects require what OS. This tries to solve that. Change-Id: I1fb2912ec49f5bc2781853e500508d9992d59fbb Signed-off-by: Fatih Degirmenci <fatih.degirmenci@ericsson.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>