Jump to: navigation, search

Difference between revisions of "IBM/IBM DB2 CI"

(Issue Tracker)
Line 16: Line 16:
  
 
== Issue Tracker ==
 
== Issue Tracker ==
If you got any issues of this DB2-TEST CI, please contact "yanfengxi@cn.ibm.com"
+
If you got any issues of this DB2-TEST CI, please contact "yanfengxi@cn.ibm.com", or reach irc account "yanfengxi" on channel #openstack-infra.
  
 
There are currently some known issues with the ibm-db-sa library running with newer versions of sqlalchemy:
 
There are currently some known issues with the ibm-db-sa library running with newer versions of sqlalchemy:
 
* Issue 157: sql.true() does not work for IBM DB2  https://code.google.com/p/ibm-db/issues/detail?id=157
 
* Issue 157: sql.true() does not work for IBM DB2  https://code.google.com/p/ibm-db/issues/detail?id=157
 
* Issue 158: OpenStack database migrations fail with SQLAlchemy 0.9.6 and ibm-db-sa 0.3.1  https://code.google.com/p/ibm-db/issues/detail?id=158
 
* Issue 158: OpenStack database migrations fail with SQLAlchemy 0.9.6 and ibm-db-sa 0.3.1  https://code.google.com/p/ibm-db/issues/detail?id=158

Revision as of 09:39, 15 June 2015

DB2-TEST CI

DB2-TEST is a continuous integration for OpenStack running on DB2 backend. With a pipeline, DB2-TEST 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

The DB2 third party CI is being transitioned to the US due to issues with firewall restrictions in China.

Triggering Methods

The DB2-TEST 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 DB2-TEST CI, please contact "yanfengxi@cn.ibm.com", or reach irc account "yanfengxi" on channel #openstack-infra.

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