Fineract Build & Cucumber tests (without E2E tests) / verify (main, build-core) (push) Canceled after 0s
Fineract Docker Builds / build (false, docker-compose-postgresql.yml, postgresql) (push) Canceled after 0s
Fineract Docker Builds / build (true, docker-compose.yml, mariadb) (push) Canceled after 0s
Fineract Documentation build / build (push) Canceled after 0s
Fineract E2E Tests / E2E Tests (Shard 1 of 10) (push) Canceled after 0s
Fineract E2E Tests / E2E Tests (Shard 10 of 10) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - MariaDB / test (test-core-1) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - MariaDB / test (test-core-2) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - MariaDB / test (test-core-4) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - MariaDB / test (test-core-5) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - MySQL / test (test-core-1) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - MySQL / test (test-core-2) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - MySQL / test (test-core-3) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - MySQL / test (test-core-4) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - MySQL / test (test-core-5) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - PostgreSQL / test (test-core-1) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - PostgreSQL / test (test-core-2) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - PostgreSQL / test (test-core-3) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - PostgreSQL / test (test-core-4) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - PostgreSQL / test (test-core-5) (push) Canceled after 0s
Fineract Liquibase Only mode - PostgreSQL / test (push) Canceled after 0s
Fineract Messaging Smoke Tests / Smoke Test with ActiveMQ (push) Canceled after 0s
Fineract Messaging Smoke Tests / Smoke Test with Kafka (push) Canceled after 0s
Fineract Build & Cucumber tests (without E2E tests) / verify (main, cucumber) (push) Canceled after 0s
Fineract Build & Cucumber tests (without E2E tests) / verify (progressive-loan, build-progressive-loan) (push) Canceled after 0s
Fineract E2E Tests / E2E Tests (Shard 2 of 10) (push) Canceled after 0s
Fineract E2E Tests / E2E Tests (Shard 3 of 10) (push) Canceled after 0s
Fineract E2E Tests / E2E Tests (Shard 4 of 10) (push) Canceled after 0s
Fineract E2E Tests / E2E Tests (Shard 5 of 10) (push) Canceled after 0s
Fineract E2E Tests / E2E Tests (Shard 6 of 10) (push) Canceled after 0s
Fineract E2E Tests / E2E Tests (Shard 7 of 10) (push) Canceled after 0s
Fineract E2E Tests / E2E Tests (Shard 8 of 10) (push) Canceled after 0s
Fineract E2E Tests / E2E Tests (Shard 9 of 10) (push) Canceled after 0s
Fineract Cargo & Unit- & Integration tests - MariaDB / test (test-core-3) (push) Canceled after 0s
Migration-hygiene fixes found while auditing whether a fresh database would
end up with the same schema/permissions/roles as this dev database.
1. Remove fake test-data seed migrations
0449_seed_aml_test_alerts.xml and 0459_seed_aml_alerts_awaiting_review.xml
unconditionally inserted 3 fictional clients (CLIENT_RAJESH/SONIA/VIKRAM)
and 5 fake AML alerts against them on every environment, including
production if this migration path ever ran there. 0459's own comment
confirms it was written purely to exercise the AML review UI. Deleted
both files and their <include> entries; cleaned the same fake rows out
of this dev database (3 clients, 5 alerts, plus the now-orphaned
databasechangelog bookkeeping rows for the two deleted files).
2. Backfill 3 permissions lost to a migration-number collision
Auditing all 2712 changesets applied to this dev database against the
current codebase found 18 changeset filenames with no matching file
anywhere in git; changelog-tenant.xml itself already documents the root
cause (multiple branches independently reusing the same numeric prefix
for unrelated migrations, e.g. 0456-0462 twice). Cross-checking each
affected table/permission against actual Java usage (@CommandType
handlers, domain/API classes, and both permission-insert styles used in
this codebase -- Liquibase <insert> columns and raw <sql> literals)
showed 15 of the 18 are genuinely dead (reconciliation-batch/settlement-
cycle prototype tables, fixed asset/inventory tracking) with zero
current code referencing them, so nothing to backfill there. The
remaining 3 -- MENU_RECONCILIATION, READ_RECONCILIATION,
SIDEBAR_RECONCILIATION -- gate a live module (CashReconciliation /
ClearingReconciliation have real API resources and domain classes) but
were never seeded by any migration; without them a fresh database can
build and expose the reconciliation screens with no way to grant a role
access to them. Added 0491_add_reconciliation_menu_permissions.xml.
3. Merge two pairs of redundant roles
- "Bank Cashier" (4 fund-transfer permissions, 0 of which overlapped
"CASHIER", 0 users assigned) folded into CASHIER.
- "AML Officer" (2 permissions, both already present on "Principal
Officer", 0 users assigned) folded into Principal Officer.
Both migrations copy any missing permissions and move any assigned
users onto the surviving role before deleting the redundant one, so
they're safe to run against an environment that isn't empty the way
this dev database is. Applied the same merge directly to this dev
database's m_role / m_role_permission / m_appuser_role rows.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>