Age | Commit message (Collapse) | Author | Files | Lines |
|
Change-Id: I81eaed8b397b5d748c5fde5a07dadecde0ec08fa
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
|
|
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>
|
|
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>
|
|
Change-Id: I4b30765b243e2a1a6d2079b71fc6d18c14853dec
Signed-off-by: 00184532 <lu.yao135@zte.com.cn>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
Change-Id: I5193285493926fcf82779f12d491a118bc83baa7
Signed-off-by: 00184532 <lu.yao135@zte.com.cn>
|
|
Leave more time for ODL debug.
Change-Id: I614a8f8ef088f687f71405365dce6cccaaef741c
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
Change-Id: I0f20005873aac6c7c4f7e3baf04fab56f38b14df
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
|
|
|
|
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>
|
|
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>
|
|
JIRA: RELENG-254
Change-Id: I71f2879dd04cc56dc8023fc7163871e94de78eb6
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Zte-pod2 is a little busy.
Change-Id: I7628a1a966552c5caf1706a2ac8c47952a11c095
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
Change-Id: I8c0c088c5b6879033e1d369488b589271e741a68
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
Change-Id: I9c9759f3f361d6e0e56429e0aeca6205fa59934f
Signed-off-by: Zhijiang Hu <hu.zhijiang@zte.com.cn>
|
|
Leave more time for debugging on nosadn-nofeature scenario.
Change-Id: I38199954ddd503c5bf4e956ae97ae61a470a2ad8
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
deployment and integration with functest
Change-Id: Ic9f72f4f6bf4d526b51b3254cfc2efd5842dd58c
Signed-off-by: Julien <zhang.jun3g@zte.com.cn>
|