1 Commits (bfe02339b34cfe83a4efcad436edadfe71656d55)

Author	SHA1	Message	Date
Chaoyi Huang	da6c08f93e	Add hook scripts for the Jenkins job for Tricircle tempest ... 1.What is the purpose of this patch set? The Tricircle project doesn't provide integration test yet. To achieve integration test, the Tricircle needs to provide hook scripts for the Jenkins job to execute the test. The Tricircle integration test Jenkins job will be configured in https://github.com/openstack-infra/project-config/tree/master/jenkins/jobs A Jenkins job patch will be submited to project-config once this patch is merged. Without the hook scripts provided in this patch, the Jenkins job configured in project-config is not able to be executed successfully. After the autotimc Jenkins job is established, all new patches sumitted to the Tricircle should pass the integration test, i.e. the test is also the gate test for a new patch. For example, for cinder volume type patch, currently no integration test is provided, we don't know the patch work or not. As new features added to the Tricircle, integration test cases from the Tempest for OpenStack Nova/Cinder/Neutron could be added to the post_test_hook.sh, to test the features added to the Tricircle is correct or not. 2.What is the benefit of this patch set for the Tricircle project? Reuse OpenStack Nova/Cinder/Neutron tempest test cases, and provide integration gate test for new patches. 3.What is the platform you tested it out? After the Jenkins job patch is merged, the test will be executed in the OpenStack CI pipeline, and as one of the gate test for a new patch. CI pipeline will be triggered by gerrit review process, and the test will be executed in the devstack VM(booted by CI pipeline). http://docs.openstack.org/infra/system-config/jenkins.html Change-Id: I5333681fdcaefb01498d9d8c6751d5d174bf57c2 Signed-off-by: Chaoyi Huang <joehuang@huawei.com>	7 years ago