Difference between revisions of "ThirdPartySystems/Quobyte CI"
(Updated on CI migration status) |
m |
||
Line 9: | Line 9: | ||
<br> | <br> | ||
'''2016-01-26 - Cinder and OS-Brick CIs are currently migrating to new and more capable hardware. A new Nova CI will be added to this setup in the process. Later on migration of the Manila CI will follow up.''' | '''2016-01-26 - Cinder and OS-Brick CIs are currently migrating to new and more capable hardware. A new Nova CI will be added to this setup in the process. Later on migration of the Manila CI will follow up.''' | ||
− | * '''Update 2015-01-28: basic system setup has been completed. | + | * '''Update 2015-01-28: basic system setup has been completed. Configuring CI job details and testing now.''' |
<br> | <br> | ||
<br> | <br> |
Revision as of 13:32, 28 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 (down), OS-Brick project (down) 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.