Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/IBM DB2 CI"

(Excluded Tests)
(Current Status)
Line 6: Line 6:
 
== Current Status ==
 
== Current Status ==
  
The DB2 third party CI is being transitioned to the US due to issues with firewall restrictions in China.
+
'''a. Jobs'''
 +
 
 +
'''Enabled and published:''' cinder, ironic, heat, neutron
 +
 
 +
'''Enabled, not published:''' Keystone (Reason: needs community's review and agreement.)
 +
 
 +
Glance CI is enabled but only publishes test result to one patch(167101) (Reason: Community bug 1434440 and RTC issue: 197295)
 +
 
 +
Nova CI only publish result to in-progress patch https://review.openstack.org/#/c/69047/
 +
 
 +
'''b. Infrastructure'''
 +
 
 +
Now, DB2 CI is suffering from so limited hardware resource. Because of this, DB2 CI can not handle so many community patches, which results in the fact that only a few patches got tested.
 +
 
 +
To solve this, we are trying to added more clouds in as the slave nodes provider.
  
 
== Triggering Methods ==
 
== Triggering Methods ==

Revision as of 04:02, 14 May 2015

IBM DB2 CI

IBM DB2 CI is a continuous integration for OpenStack running on DB2 backend. With a pipeline, DB2 CI listens to newly created patch sets on review.openstack.org and runs the Tempest test suites on the patch.

In the case of sqlalchemy-migrate, py26 and py27 unit tests are also run.

Current Status

a. Jobs

Enabled and published: cinder, ironic, heat, neutron

Enabled, not published: Keystone (Reason: needs community's review and agreement.)

Glance CI is enabled but only publishes test result to one patch(167101) (Reason: Community bug 1434440 and RTC issue: 197295)

Nova CI only publish result to in-progress patch https://review.openstack.org/#/c/69047/

b. Infrastructure

Now, DB2 CI is suffering from so limited hardware resource. Because of this, DB2 CI can not handle so many community patches, which results in the fact that only a few patches got tested.

To solve this, we are trying to added more clouds in as the slave nodes provider.

Triggering Methods

The DB2 CI can be triggered by newly-uploaded patch set, or by leaving a commnand "recheck db2-test" in comments.

Excluded Tests

A small handful of Tempest tests are excluded from run because there are known issues or a specific feature may not be implemented. Information about these tests can be found here.

Issue Tracker

If you got any issues of this IBM DB2 CI, please contact "yanfengxi@cn.ibm.com"

There are currently some known issues with the ibm-db-sa library running with newer versions of sqlalchemy: