hi Magnum hackers:
Currently there is a pip line on project-config to do magnum functional
testing [1]
on summit, we've discussed that we need to split it per COE[2], we can
do this by adding new pip line to testing./
/ /- '{pipeline}-functional-dsvm-magnum{coe}{job-suffix}':/
coe could be swarm/mesos/k8s,
then passing coe in our post_test_hook.sh [3], is this a good idea?
and I still have others questions need to be addressed before split
functional testing per COE:
1 how can we pass COE parameter to tox in [4], or add some new envs like
[testenv:functional-swarm] [testenv:functional-k8s] etc?
stupid?
2 also there are some common testing cases, should we run them in all
COE ?(I think so)
but how to construct the source code tree?
//functional/swarm//
///functional/k8s//
///functional/common ../
[1]https://github.com/openstack-infra/project-config/blob/master/jenkins/jobs/projects.yaml#L2288
[2]https://etherpad.openstack.org/p/mitaka-magnum-functional-testing
[3]https://github.com/openstack/magnum/blob/master/magnum/tests/contrib/post_test_hook.sh#L100
[4]https://github.com/openstack/magnum/blob/master/tox.ini#L19
--
BR, Eli(Li Yong)Qiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151103/b894c4f0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: liyong_qiao.vcf
Type: text/x-vcard
Size: 123 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151103/b894c4f0/attachment.vcf>