Skip to content
 
 

Latest commit

 

History

30,210 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

CUBRID continuous testing for Hibernate ORM

This is a fork of hibernate/hibernate-orm that CUBRID Inc. uses to test CUBRIDDialect every day.

CUBRIDDialect is part of hibernate-community-dialects. Hibernate's own CI does not run community dialects, so a Hibernate change that breaks CUBRID could go unnoticed until a release. This fork runs the full test suite against CUBRID every day to catch that early.

What runs

Schedule Every day at 18:30 UTC
CUBRID versions 10.2, 11.0, 11.2, 11.3, 11.4, and the latest development build
JDBC driver The released driver from Maven Central. The development build uses the driver it ships with
Scope ./gradlew ciCheck --continue, the same goal Hibernate uses for its own database jobs. --continue lets the other modules run after the known failures in hibernate-core
Source This fork's main, which a daily job keeps in sync with hibernate/main

Results and test reports for each version are on the CUBRID CI page.

Reading the results

Tests that fail because of a CUBRID JDBC driver defect or a Hibernate issue are not skipped. They stay failing until the fix is released, and then pass without any change here, so a red run on its own does not mean that something new broke. The Report job at the end of each run compares it with the previous scheduled run and lists the tests that started or stopped failing, with what changed in between: the Hibernate commits, the JDBC driver, the CUBRID engine build and the runner.

The known failures and excluded tests are tracked in TOOLS-4940 (in Korean).

Daily report

Every scheduled run posts its report as an issue labelled ci-report. The title gives the outcome, for example CUBRID CI 2026-11-10: 1 new failure, 11 fixed. Issues with new failures or missing results stay open until someone has looked at them, and the others are closed as soon as they are posted.

To get the report by email, watch this repository with Custom and Issues selected.

Tests that do not run

When CUBRID does not support a feature, the test is excluded with a DialectFeatureCheck, the same way Hibernate handles other databases. A few tests are skipped by dialect name, each with the reason.

This is not a distribution

Nothing is published from this fork. Use the official artifacts:

implementation 'org.hibernate.orm:hibernate-core'
implementation 'org.hibernate.orm:hibernate-community-dialects'

Dialect changes go upstream through Hibernate's JIRA and pull requests. They are not kept here.

Contact

Maintained by CUBRID Inc. For dialect issues, open an issue on hibernate.atlassian.net, or reach us through cubrid.org.