OpenStack CI Loop for Xen-Libvirt
|
To Do:
Put the content of this page together - aka a user manual for how to interpret results and how to investigate issues |
CI Loop
This article provides some information about jenkins.openstack.xenproject.org, which is the front-end for the Xen Project OpenStack CI loop, which is a 3rd party OpenStack CI loop (3rd party because it is operated by the Xen Project, not the OpenStack Foundation). You can find more information about 3rd party OpenStack testing systems in the following articles
- Setting Up an External OpenStack Testing System – Part 1
- Setting Up an External OpenStack Testing System – Part 2
- The Test Suite we run (OpenStack Tempest)
- Tempest Overview
Baseline
Usage Instructions
Our OpenStack CI loop interface is available at jenkins.openstack.xenproject.org. Currently we are ramping up and the CI loop is not yet voting on OpenStack Nova. In other words, changes to OpenStack Nova which break Xen, will not be automatically rejected. Bot hopefully, this will happen soon.
The CI loop tests our baseline against each Nova OpenStack commit.
Dashboard
The most useful view to get an overview over test failures can be found at the Build History page.
OpenStack review: Each build maps onto a changeset on [1]. The following figure shows how to map a test run on our CI loop to a specific OpenStack review.
Aborted builds: Sometimes, jobs are aborted. The main reason for aborted jobs is that the OpenStack CI loop run at the OpenStack Foundation (or another voting 3rd party CI loop) may have determined that a change breaks a test. In other words, it is not necessary to complete the test in this case. Aborted jobs are typically marked with a grey circle. Note that this is nothing to worry about
Checking up on Test Failures
Community Activities
Training Session (week of May 4th)
We are planning a training session the week of May 4th or the week after, For more details see here. This will also include a discussion on how to integrate the CI loop into the project's workflow.
