Difference between revisions of "ThirdPartySystems/Quobyte CI"
m |
(Updated recheck command info) |
||
| Line 19: | Line 19: | ||
=== Rechecking Quobyte CI Systems === | === Rechecking Quobyte CI Systems === | ||
| − | All CI systems run by Quobyte support rechecking by adding the comment ' | + | All CI systems run by Quobyte support rechecking by adding the comment 'run <ci-instance-name>' to the patch set in question. |
For example: | For example: | ||
<nowiki> | <nowiki> | ||
| − | + | run cinder-quobyteci-dsvm-volume | |
</nowiki> | </nowiki> | ||
This command works even if there's no previous report from the given CI instance for the given patch set. | This command works even if there's no previous report from the given CI instance for the given patch set. | ||
Revision as of 06:24, 22 September 2015
| Gerrit Account: quobyteci | |
| Contact Information: silvan@quobyte.com (kaisers@IRC), robert@quobyte.com (mrlarkin@IRC), felix@quobyte.com, bjoern@quobyte.com, | |
| Intent: Test Cinder, 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. Similar installations testing nova and manila changes with their respective tempest tests on a quobyte backend based setup. Working on openstack/nova and openstack/manila CI setups. | |
| OpenStack Programs: Cinder, Manila, (Nova to be added) | |
| Current Status: Reporting in Cinder project (stable), testing in Manila and in sandbox project (currently unstable) Bugs/changes affecting the Cinder CI results:
|
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.
