Make OpeNMetadata Service Unit Test Required

[mohityadav766]

Describe your changes:

Fixes

I worked on ... because ...

Type of change:

• Bug fix
• Improvement
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation>
• I have commented on my code, particularly in hard-to-understand areas.
• For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

[gitar-bot]

Code Review ✅ Approved

Makes the OpenMetadata Service Unit Test required in the CI/CD pipeline. No issues found.

Options

Display: compact → Showing less information.

Comment with these commands to change:

Compact

gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[Copilot]

Pull request overview

This PR updates the GitHub Actions workflow for OpenMetadata service unit tests to run the Maven test job across a database matrix (MySQL and PostgreSQL), with per-database test report naming to support branch protection / required-check gating.

Changes:

• Add a matrix strategy to run openmetadata-service unit tests for mysql and postgresql.
• Include the database selector in the Maven profile list and in artifact / test report check naming.

[Copilot]

The matrix adds -P... ,${{ matrix.database }} but Maven profiles mysql/postgresql don’t appear to be defined in the root pom.xml or openmetadata-service/pom.xml (they only exist in openmetadata-sdk/pom.xml). With mvn ... -pl openmetadata-service -am, those profiles are likely not available/active, so this will run the same unit test suite twice and won’t actually switch database behavior.

Consider either defining these profiles in the root/service POM (so they apply to this build) or passing an explicit property/env that the service tests actually consume (e.g., -Dtest.database=...) and wiring tests to use it.