Difference between revisions of "IBM/IBM DB2 CI"
(→DB2-TEST 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" | ||
+ | |||
+ | 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 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 17:05, 14 July 2014
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
Currently, DB2-TEST CI is only open to sqlalchemy-migrate, keystone, cinder and glance projects.
Because the development of DB2 support of nova is still working in progress, DB2-TEST is only open to some specific nova patch sets, mainly https://review.openstack.org/#/c/69047/ by Matt Riedemann.
This Heat patch is needed for DB2 CI to work on Heat patches: https://review.openstack.org/#/c/98733/
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"
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 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