Difference between revisions of "Midokura-third-party-testing"
Line 16: | Line 16: | ||
==System Setup== | ==System Setup== | ||
− | Currently MTPT runs on Jenkins | + | Currently, MTPT runs check-tempest-neutron-midonet-plugin job on a CI system based on Jenkins, Zuul, Gearman and Nodepool to meet the OpenStack requirements. |
MTPT is voting +1 on a success and 0 on a failure. | MTPT is voting +1 on a success and 0 on a failure. | ||
− | + | To retrigger a build post a comment with "recheck midokura" | |
==List of Publicly Available Logs== | ==List of Publicly Available Logs== |
Revision as of 07:45, 12 August 2014
Introduction
Midokura Third-Party Testing (MTPT) runs a set of Tempest tests on every new patch submitted for review to the upstream master branch of the OpenStack Neutron project. The patch is tested using the Midonet plugin on a Devstack environment to ensure that the patch works with it.
The OpenStack gerrit account name for MTPT is “Midokura CI Bot”.
System Setup
Currently, MTPT runs check-tempest-neutron-midonet-plugin job on a CI system based on Jenkins, Zuul, Gearman and Nodepool to meet the OpenStack requirements.
MTPT is voting +1 on a success and 0 on a failure. To retrigger a build post a comment with "recheck midokura"
List of Publicly Available Logs
Public logs for the testing results are stored in: http://3rdparty-logs.midokura.com/
Contact Information
For any questions or comments, please contact: mido-openstack-dev@midokura.com