Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/CloudByte CI"

(Set to maintenance due to lab movement)
(Set to maintenance due to lab movement)
Line 6: Line 6:
 
|method=Using Zuul to connect to Gerrit, trigger Jenkins job to run DevStack, then Tempest volume API and basic scenario tests.
 
|method=Using Zuul to connect to Gerrit, trigger Jenkins job to run DevStack, then Tempest volume API and basic scenario tests.
 
|programs=Cinder, Tempest
 
|programs=Cinder, Tempest
|status=Stable, Non-Voting}}
+
|status=Under Maintenance}}
'''Recheck trigger:''' "Under Maintenance"
+
'''Recheck trigger:''' "recheck cloudbyte"

Revision as of 09:53, 27 September 2016

3rd party system: CloudByte CI
Gerrit Account: CloudByteCI
Contact Information: openstack-dev@cloudbyte.com, punith.s@cloudbyte.com, amit.das@cloudbyte.com,brijnandan@cloudbyte.com, abhishek@cloudbyte.com
Intent: Testing CloudByte Cinder driver.
Structure: Jenkins, Zuul, Gearman, Static DevStack Slave
Method: Using Zuul to connect to Gerrit, trigger Jenkins job to run DevStack, then Tempest volume API and basic scenario tests.
OpenStack Programs: Cinder, Tempest
Current Status: Under Maintenance


Recheck trigger: "recheck cloudbyte"