summaryrefslogtreecommitdiffstats
path: root/jjb/daisy4nfv/daisy-daily-jobs.yml
AgeCommit message (Collapse)AuthorFilesLines
2018-04-13Merge "Enable all yardstick tasks on baremetal for daisy"Serena Feng1-3/+0
2018-04-13Merge "[daisy] Move more CI resource to Fraser branch"Serena Feng1-4/+4
2018-04-13Enable all yardstick tasks on baremetal for daisyJulien1-3/+0
currently only master job is enabled. Change-Id: I7da6a1a3a8e8faf08cde34d9a20219346070151b Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2018-04-12[daisy] Move more CI resource to Fraser branchZhijiang Hu1-4/+4
Temporary disable master branch job on zte-pod2 to make room for Fraser branch job. Change-Id: I9f2eea0e1c85eab741f80e6db6b773eec71c39f1 Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
2018-04-11Move DEPLOY_SCENARIO out of testapi-parametersTrevor Bramwell1-0/+2
These have been moved back into installer-params.yml and added to the daisy jobs where 'testapi-parameters' is being used. Including this in the list of parameters would cause duplication as most installers already include 'DEPLOY_SCENARIO' as a parameter. The 'DEPLOY_SCENARIO' parameter is also sometimes defined through a macro, which could cause second declaration of DEPLOY_SCENARIO (defaulting to 'os-nosdn-nofeature-ha') to always be used. Documentation has been added to the parameter to explain the related macros and how they should be used. Change-Id: I9aef031dbcf523ae2db15695ce294bd85025530d Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2018-04-03[daisy]Enable jobs for stable/fraser branchZhijiang Hu1-27/+52
Now we have had the stable/fraser branch in place [1]. Let's Re-arrange CI resources for it. [1] https://gerrit.opnfv.org/gerrit/#/c/54693/ Change-Id: Id596b1070c781da4edfd2496a47ea36400268614 Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
2018-03-16[daisy] Fix the blocking rules of daisy daily jobsAlex Yang1-2/+2
Change-Id: I81eaed8b397b5d748c5fde5a07dadecde0ec08fa Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
2018-03-14Merge "add another ovs_dpdk scenarios trigers"Fatih Degirmenci1-1/+1
2018-03-12Update block rules on nodesJulien1-1/+3
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-12Define parameters for triggering jobsJulien1-15/+2
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-07Update return value from postbuildscriptJulien1-0/+9
PostBuildScript plugin's result affects Jenkins pipeline, so we should return the original job running status in the postbuildscript in the end Update macros: 1. from $POD_NAME to $NODE_NAME 2. from $SCENARIO to $DEPLOY_SCENARIO 2. {installer} to $INSTALLER_TYPE for {installer} is not existed in trigger job 3. add parameters definition for they can not be used in trigger jobs by predefined-parameters 4. missing TIMESTAMP_END Change-Id: I354be3d5ad02e53bb988995adc09b59e92a1640a Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2018-02-13[daisy] Move master branch jobs to zte-pod2Zhijiang Hu1-11/+11
This PS does: 1) Move master branch jobs to zte-pod2 which seems has a more stable internet connectivity. This is trying to solve master branch deployment unstable problem. 2) Disable Euphrates jobs to make room for master branch. Change-Id: Id36f0ff6a268aabf0badd46f55bb397afe5e4830 Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
2018-01-16[daisy] Add '|' for more than one predefined-parametersZhijiang Hu1-3/+3
This tries to solve Job name error [1] which cause functest failure. [1] https://build.opnfv.org/ci/job/functest-daisy-baremetal-daily-master/257/console Change-Id: I89c9a00bcaf0ccb274a18339533bdd99b1134be3 Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
2018-01-15Add macro for reporting the provision resultJulien1-0/+12
1. add macro for report the provision result of installers and try it in daisy 2. update according to TestAPI interface Change-Id: Ic041744c917c37fcd84a12a92e927e39106cf18f Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2018-01-11[daisy] Enable ovs_dpdk scenarios jobs001845321-1/+50
Change-Id: I5193285493926fcf82779f12d491a118bc83baa7 Signed-off-by: 00184532 <lu.yao135@zte.com.cn>
2018-01-10[daisy] Adjust the schedule of daisy master jobsAlex Yang1-2/+2
Leave more time for ODL debug. Change-Id: I614a8f8ef088f687f71405365dce6cccaaef741c Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
2017-11-06[daisy] Prevent CI jobs run on the same POD parallellyZhijiang Hu1-0/+1
Change-Id: I0f20005873aac6c7c4f7e3baf04fab56f38b14df Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
2017-11-03Merge "[Daisy] Add docker image tarball builder"Trevor Bramwell1-0/+2
2017-10-28[Daisy] Add docker image tarball builderZhijiang Hu1-0/+2
This PS do: 1. Add docker image tarball builder as a Daisy project job. Name is daisy-kolla-build-.* 2. Upload image to artifact storage after building. 3. Fix new job runs on daisy-virtual. 4. Block jobs with each other which may run Daisy VM because VM has the same name. Change-Id: I148473ca33f1e10490684b7608354a4ba548714f Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
2017-10-19Integrate yardstick on daisy master branchAlex Yang1-1/+22
JIRA: DAISY-9 1. Trigger yardstick job in daisy-baremetal-daily-master on zte-pod3 2. Add daisy pods in yardstick 3. Add EXTERNAL_NETWORK in installer params Change-Id: Ia8e69e503102c1fb282d6d2c5acac2ac3cbfe747 Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
2017-10-03Fix Yamllint violations for jjb/daisy4nfvTrevor Bramwell1-149/+155
JIRA: RELENG-254 Change-Id: I71f2879dd04cc56dc8023fc7163871e94de78eb6 Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
2017-09-28Move daisy jobs of master branch to zte-pod3Alex Yang1-3/+6
Zte-pod2 is a little busy. Change-Id: I7628a1a966552c5caf1706a2ac8c47952a11c095 Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
2017-09-22Enable daisy euphrates jobs of daily and functestAlex Yang1-0/+16
Change-Id: I8c0c088c5b6879033e1d369488b589271e741a68 Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
2017-09-13Enable jobs for stable/euphrates branchZhijiang Hu1-0/+33
Change-Id: I9c9759f3f361d6e0e56429e0aeca6205fa59934f Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
2017-08-24Adjust the schedule of daisy jobsAlex Yang1-2/+2
Leave more time for debugging on nosadn-nofeature scenario. Change-Id: I38199954ddd503c5bf4e956ae97ae61a470a2ad8 Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
2017-08-24Adjust the schedule of daisy baremetal jobsAlex Yang1-2/+2
Now the functest NFV testcases only run in nosdn-nofeature scenario. So we adjust the schedule to leave more time for debugging on these testcases. Change-Id: I37425a86c7359b57cb7048dc1339acb7ea8cb525 Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
2017-08-09Rename odl_l3 to odlZhijiang Hu1-22/+9
Rename all scenarios with "odl_l3" in their name in Euphrates to just "odl". Change-Id: If2bff0da79f79b9305771d2fc575db1606cd4bf9 Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
2017-07-26Enable daisy HA deployment jobAlex Yang1-13/+13
In patch https://gerrit.opnfv.org/gerrit/#/c/36873/ daisy noha jobs were added since the HA function is not perfect at that time. Now the issues have been fixed and HA function can be enabled. Change-Id: I1fc9a235191ba47e8473ae8a429994dc36cca955 Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
2017-07-04Enable ODL scenarios jobsZhijiang Hu1-2/+28
This PS does the follwoing things: 1. Enable ODL scenarios jobs on CI Pod 2. Change default scenario from ha to noha Change-Id: I548174bfa551aa06b6d9bfe64cf119eea37efda3 Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
2017-04-01Update block parametersJulien1-1/+0
Fix issue: 1. father job block child jobs 2. deploy the env in daisy-virtual slaves Change-Id: Idcda4b8ca5fcf9abbfae3c60bf656a0901a20e02 Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2017-03-23Avoid build conflicts in build serverJulien1-1/+2
Currently each job in daisy project has multiple child jobs, which may block the resources in lf-build1 for the excutors are limited. Change-Id: I7977128a550421caaeda395fce04b91b31d35751 Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
2017-02-22Add scenarios jobsJulien1-0/+199
deployment and integration with functest Change-Id: Ic9f72f4f6bf4d526b51b3254cfc2efd5842dd58c Signed-off-by: Julien <zhang.jun3g@zte.com.cn>