summaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2018-03-15Merge "xci: Skip the deployment for upstream and prototype changes"Fatih Degirmenci1-0/+4
2018-03-15Merge "run prepare-functest on opnfv vm"Fatih Degirmenci1-1/+1
2018-03-15xci: Skip the deployment for upstream and prototype changesFatih Degirmenci1-0/+4
Changes coming to these do not impact the framework so there is no need to run full verification for these. Change-Id: Ia9f8f4772a94cb0761c49ff27933798265831fa4 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-15run prepare-functest on opnfv vmPeriyasamy Palanisamy1-1/+1
Change-Id: Ide49917687ed583497ca089969fd2c7e7e00e548 Signed-off-by: Periyasamy Palanisamy <periyasamy.palanisamy@ericsson.com>
2018-03-15xci: Do not run deployment for doc updatesFatih Degirmenci1-0/+2
Change-Id: Ic914bc5bf11e2246f214990353c804688d6e43d9 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-14Merge "xci: Create post merge jobs to promote scenarios"Fatih Degirmenci3-70/+226
2018-03-14Merge "add another ovs_dpdk scenarios trigers"Fatih Degirmenci1-1/+1
2018-03-14Merge "Rename project to 'yardstick' from 'yardstick-arm64'"Fatih Degirmenci1-1/+1
2018-03-14xci: Create post merge jobs to promote scenariosFatih Degirmenci3-70/+226
This change lays down the basic job structure for post merge promotion jobs. The job structure will be - a top level multijob job that is scenario specific and can not run concurrently. This job runs distro deploy and test jobs for all the distros in the first phase concurrently, followed by a common promote job. - the deploy and test jobs are same as the xci-verify jobs except the trigger. They are triggered by top level multijob. - the promote job is run once all the deploy & test phase jobs successfully completed, uploading promotion metadata to artifacts.opnfv.org. The builders except set-scenario are left empty in order to try the basic job setup first. Followup changes will get real things in. Once the basics are in place, the first promotion will be done using functest healthcheck and then we will start working on gating scenarios for promotion using functest smoke and perhaps feature test cases. Change-Id: Ib91ffe0f3003b86841a62537c52fde176cafa70f Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-14Merge "add daisy installer for doctor verify jobs"Ryota Mibu2-13/+27
2018-03-14Merge "Update block rules on nodes"Serena Feng2-1/+10
2018-03-13Build functest-xtesting imagesDelia Popescu3-7/+225
Build and push xtesting images Create manifests for xtesting images Build xtesting images for arm JIRA: FUNCTEST-948 Change-Id: I3fbe6cdfef5b304a45d76533417f3c4bc58dddbe Signed-off-by: Delia Popescu <delia.popescu@enea.com>
2018-03-13Move functest docker job in functest dirCédric Ollivier1-0/+0
Change-Id: I454c327f3359688742b5d8c4299efee05d6494a2 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-03-13Merge "xci: Allow specifying scenario and installer in commit message"Fatih Degirmenci1-20/+68
2018-03-13xci: Allow specifying scenario and installer in commit messageFatih Degirmenci1-20/+68
It is not always practical to try determining scenario and installer to run jobs programmatically. This change adds possibility to do that by parsing commit message and skipping the automatic scenario and installer extraction. Change-Id: I10c9620fe8bb69a2d69fceb31d08084265aa1d75 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-13jjb: xci: Ensure GERRIT_TOPIC is always setMarkos Chandras4-0/+12
Fixes the following problem [description-setter] Description set: Scenario: os-nosdn-nofeature | Node: intel-virtual14 [xci-verify-ubuntu-healthcheck-virtual-master] $ /bin/bash /tmp/jenkins7521920744845291696.sh /tmp/jenkins7521920744845291696.sh: line 21: GERRIT_TOPIC: unbound variable Build step 'Execute shell' marked build as failure Change-Id: Iddf82e6ae6c6c433d941c461953c11935bc45269 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-13Merge "Update Functest jjobs (patrole)"Jose Lausuch2-9/+2
2018-03-13Update Functest jjobs (patrole)Cédric Ollivier2-9/+2
Patrole is now integrated in smoke and the dedicated container is being removed [1] [1] https://gerrit.opnfv.org/gerrit/#/c/53659/ Change-Id: Ifb1989c5e430a4bf0fdd553f2e3e82f69a704f25 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-03-13jjb: xci: Allow CI to run when multiple components are affectedMarkos Chandras1-0/+7
Sometimes we make global changes that affect multiple components at once and splitting that is not possible because it needs to be shipped as an atomic change. As such, allow topics with 'force-verify' to run the CI using the default installer and scenario. Change-Id: Ie4753822111b20c4f479886a55fe569c9b91ccd0 Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-12Merge "Temporary incease functest timeout to 360 minutes"Fatih Degirmenci1-2/+2
2018-03-12xci: Combine vars setting installer type in INSTALLER_TYPEFatih Degirmenci2-5/+5
Change-Id: I5312ac784b1621ce968bbdfb1532859dada0e790 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-12Temporary incease functest timeout to 360 minutesDelia Popescu1-2/+2
Openstack APIs response call is tacking very long on ARM Work is being done on fixing the issue Temporary increase functest timeout on x86 too because of COMPASS JIRA: ARMBAND-366 JIRA: COMPASS-589 Change-Id: I355500da56c5a040324c0969237ac2decfd29edf Signed-off-by: Delia Popescu <delia.popescu@enea.com>
2018-03-12Merge "xci: Set installer type for the tested scenario"Fatih Degirmenci2-4/+1
2018-03-12xci: Set installer type for the tested scenarioFatih Degirmenci2-4/+1
Variables injected by envInject are set after the job variables which results in not setting the variable correctly. The Jenkins test script now uses the variable injected by envInject to set the INSTALLER_TYPE to XCI_INSTALLER. Change-Id: Id79281a2ee22d407ffb1bd7c4be1471f6f329803 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-12xci: Skip functest healtcheck if it is Kubernetes scenarioFatih Degirmenci1-0/+6
We need to work on functest healthcheck for Kubernetes scenarios. Until we get it working, healthcheck is disabled. Change-Id: If470dbe956c5859825f0829d1f8d022bdafcc242 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-12Update block rules on nodesJulien2-1/+10
Only one scenario job can be excuted in the same POD. The rules should be configured in job teamplate instead of parent job. Change-Id: I9f672345985dbfdfe54b9ccd017a3a575a2ab412 Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2018-03-12add daisy installer for doctor verify jobsdongwenjuan2-13/+27
Change-Id: I54b4015b1da9a5961c2d3ee1f672b381a3f72914 Signed-off-by: dongwenjuan <dong.wenjuan@zte.com.cn>
2018-03-12xci: Determine impacted generic scenarioFatih Degirmenci1-15/+39
Change-Id: Ifbe676cd347c2d3c68f04b5137f3ccaa83a95894 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-12xci: Set the installer and move scenario extraction into functionsFatih Degirmenci2-33/+65
The scenarios named os-* are deployed by osa and the ones named k8-* are deployed by kubespray. This change determines the installer to use by looking into the scenario name. The installers are currently hardcoded within xci-set-scenario.sh script and this needs to be fixed for other installers when they onboard to xci. Apart from setting the installer, extraction of generic and external scenarios are moved into corresponding functions. Change-Id: I19882bcd2a1260765e601ecbe517551c60401d74 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-12Merge "jjb: xci: Drop the VM cleanup step from the functest jobs"Markos Chandras2-4/+0
2018-03-12Merge "xci: Set options in run-functest.sh"Markos Chandras1-0/+3
2018-03-12jjb: xci: Drop the VM cleanup step from the functest jobsMarkos Chandras2-4/+0
We do the VM cleanup as part of the postbuild process so we do not need to have it in the functest jobs anymore. Change-Id: I64e4b58837090df33ae529232ef15a19de8f198a Signed-off-by: Markos Chandras <mchandras@suse.de>
2018-03-12Merge "jjb: xci: Add postbuild publisher script to remove clean VM"Markos Chandras5-2/+36
2018-03-12Define parameters for triggering jobsJulien2-17/+24
In https://wiki.jenkins.io/display/JENKINS/Plugins+affected+by+fix+for+SECURITY-170, it indicates that: only build parameters that have been explicitly defined in a job's configuration will be available by default at build time. Any other arbitrary parameters added to a build by plugins will not be available by default. It has been tested in sandbox.opnfv.org that only defined parameters can be passed to the triggered jobs. For parameters required by TESTAPI are common to all the projectes, including installers, Functest, and Yardstick, it is convenient to define a common macro and used by others. Change-Id: Iac1da85445e1b5d75109ccd64b174f35151b9969 Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2018-03-10add another ovs_dpdk scenarios trigers001845321-1/+1
Change-Id: I4b30765b243e2a1a6d2079b71fc6d18c14853dec Signed-off-by: 00184532 <lu.yao135@zte.com.cn>
2018-03-09Fix functest job name for armband ci jobsTrevor Bramwell1-1/+1
Change-Id: I44c47347ce8759a545245bf2d3ad6d6657226875 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-03-09Merge "Revert functest-daily-jobs.yml again"Aric Gardner1-282/+40
2018-03-09Merge "A new docker container for QTIP"Fatih Degirmenci1-0/+5
2018-03-09Revert functest-daily-jobs.yml againCédric Ollivier1-282/+40
Switching to multijob forces to increase executors which is too risky so closed to the release. It basically reverts the previous functest-daily-jobs.yml [1]. [1] git checkout 7f06f9492f4f8dd47669a553ef6e9c967fa29e8e jjb/functest/functest-daily-jobs.yml 7f06f9492f4f8dd47669a553ef6e9c967fa29e8e Change-Id: I4a461108b11effe59e49108e1d95a9aae6e81ade Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-03-09Run all tests in a specific stepCédric Ollivier1-3/+56
It bypasses the missing senquential mode. It also fixes exclusions about fds and patrole. Several Functest could run in parallel but it's impossible from the time being due to an xtables lock. Change-Id: I831a8c995efbf2484afd86785f17f51981c921c1 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-03-08Fix a typo which runs all jobs in parallelCédric Ollivier1-1/+1
Change-Id: I454ff72c377a96aa769919348b27813ad434eb89 Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
2018-03-08functest: Enable jobs per streamFatih Degirmenci1-1/+3
Change-Id: I5289fedf52354f2cef6a3202df27d35acccb7c6c Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-08Merge "Add patrole and parser in Functest daily jobs"Fatih Degirmenci1-0/+11
2018-03-08fuel-armband: Fix functest job nameFatih Degirmenci1-1/+1
Change-Id: Iaf8918942909e2b4b9608229f3fe0374efbd9d3f Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-08Merge "fuel-armband: Add functest and yardstick as downstream jobs"Aric Gardner1-36/+22
2018-03-08fuel-armband: Add functest and yardstick as downstream jobsFatih Degirmenci1-36/+22
Change-Id: I003f760adc2cb0b4959188b7f7d676d8fdbd8bb9 Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
2018-03-08Add functest multijobs back to apex.agardner2-94/+96
fingers crossed Change-Id: I220a36ec8a6a0d95e847a5672c4d8e5c0d34c5ac Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-03-08Functest jobs are not showing upagardner2-94/+92
Remove and then re-add to see if we can get jjb merge to work Change-Id: Iff380b38bbc5a69e2850cd91a99267b6d5b1128f Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-03-08Nothing change to apex job to kick it into workingagardner2-2/+2
Change-Id: I88f33b7dcdf8f4d0a3aa3f8d46a07f10c62e6ae9 Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-03-08Merge "fuel: Add functest and yardstick as downstream jobs"Fatih Degirmenci1-36/+22