Difference between revisions of "ThirdPartySystems/Quobyte CI"
(Manila CI has more issues) |
(Manila CI is back to normal) |
||
Line 12: | Line 12: | ||
<br> | <br> | ||
Bugs/changes affecting the Manila CI results: | Bugs/changes affecting the Manila CI results: | ||
− | |||
− | |||
* While testing a fix for the issue above the CI has hit a new microversion related error, debugging this, too (2016-01-11) | * While testing a fix for the issue above the CI has hit a new microversion related error, debugging this, too (2016-01-11) | ||
* CI skips several groups of non-implemented Manila feature test groups (snapshots, etc.) based on the Manila tempest tests config parameters | * CI skips several groups of non-implemented Manila feature test groups (snapshots, etc.) based on the Manila tempest tests config parameters |
Revision as of 14:49, 13 January 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 later 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 and os-brick. Similar installation testing manila changes with their respective tempest tests on a quobyte backend based setup. | |
OpenStack Programs: Cinder, OS-Brick, Manila, (Nova to be added) | |
Current Status: Reporting in Cinder project (stable), OS-Brick project (experimental) and Manila project (stable)
|
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.