Difference between revisions of "ThirdPartySystems/Quobyte CI"
(Cinder CI hit issue) |
(Updated on Nova CI status) |
||
Line 20: | Line 20: | ||
<br> | <br> | ||
Bugs/changes affecting the Nova CI results: | Bugs/changes affecting the Nova CI results: | ||
− | * Currently | + | * Nova CI has completed basic testing and is active. Currently it hits the same issue as Cinder CI (see above) |
− | |||
}} | }} | ||
Revision as of 13:25, 1 February 2016
Gerrit Account: quobyteci | |
Contact Information: silvan@quobyte.com (kaisers@IRC), robert@quobyte.com (mrlarkin@IRC), felix@quobyte.com, bjoern@quobyte.com, | |
Intent: Test Cinder, OS-Brick, Manila, and Nova) changes against Quobyte drivers | |
Structure: ansible installed sos-ci setup with some modifications | |
Method: sos-ci monitors Gerrit event stream and triggers test builds, ansible based installation in DevStack instances, running volume related tempest tests vs. Cinder, OS-Brick, and Nova changes. Similar installation testing manila changes with their respective tempest tests on a quobyte backend based setup. | |
OpenStack Programs: Cinder, OS-Brick, Manila, and Nova | |
Current Status: Reporting in Cinder project (stable), OS-Brick project (down), Manila project (stable), and Nova project (experimental)
|
Rechecking Quobyte CI Systems
All CI systems run by Quobyte support rechecking by adding the comment 'run <ci-instance-name>' to the patch set in question. For example:
run cinder-quobyteci-dsvm-volume
This command works even if there's no previous report from the given CI instance for the given patch set.