Verifies the integrety of the projects, as builds are executed immediately after a code change was detected. This plan provides no artifiacts (use a nightly build instead).

Build: #3015 was successful Changes by daryl herzmann and Guus der Kinderen

Stages & jobs

  1. Default Stage

  2. Continuous Integration

Build result summary

Details

Completed
Queue duration
1 second
Duration
13 minutes
Labels
None
Agent
mesonet-ah.agron.iastate.edu (3)
Revision
7cf9c19b51eb2d45075065647c2daf0c16d932f1
Total tests
1909
Successful since
#2937 ()

Tests

Code commits

Author Commit Message Commit date
daryl herzmann daryl herzmann 7cf9c19b51eb2d45075065647c2daf0c16d932f1 Merge pull request #3241 from guusdk/OF-3238_CockroachDB-support-introduction
OF-3238: Add exploratory CockroachDB support
Guus der Kinderen Guus der Kinderen 2b0dee006a4a26359e2350f63833537ff16d7ccc OF-3238 (code review): CI shouldn't use TTY allocation
Guus der Kinderen Guus der Kinderen c5ac56c595b93dac1e4b19af828203ca839a0ac5 fixup
Guus der Kinderen Guus der Kinderen 155b94d0618ae924cd04837eae0cadb27ed421c6 OF-3238: Fix CockroachDB detection fallback to prevent PostgreSQL schema selection
When Openfire connects to CockroachDB through the PostgreSQL JDBC driver, database metadata can look PostgreSQL-like. In that case, Openfire could classify the database as `postgresql` and load `openfire_postgresql.sql` instead of `openfire_cockroachdb.sql`.

This change hardens detection in `DbConnectionManager` by:
- capturing JDBC URL metadata,
- preserving existing direct Cockroach string checks, and
- adding a fallback probe (`SELECT version()`) for PostgreSQL-compatible connections to detect CockroachDB reliably.

If the probe finds "cockroach" in the version string, database type is set to `cockroachdb`, ensuring Cockroach-specific install/upgrade scripts are selected.
Guus der Kinderen Guus der Kinderen 911ed94233b8b5a63ad1754c52891ee9e296411e OF-3238 (code review): database setup to handle duplicate driver name
CockroachDB and Postgres use the same driver. This adds a challenge to auto-populate the database URL in the setup page. Up until now, this was based on the driver name.

In this commit, the default port is used as a differentiator. That allows the proper data to be populated based on the database selection.

Jira issues

IssueDescriptionStatus
Unknown Issue TypeOF-3238Could not obtain issue details from Jira

Shared artifacts

Artifact File size
Unpacked project files 278 MB