FINERACT-2421: Optimize github actions workflow

[adamsaghy]

Description

Describe the changes made and why they were made. (Ignore if these details are present on the associated Apache Fineract JIRA ticket.)

Checklist

Please make sure these boxes are checked before submitting your pull request - thanks!

• Write the commit message as per our guidelines
• Acknowledge that we will not review PRs that are not passing the build ("green") - it is your responsibility to get a proposed PR to pass the build, not primarily the project's maintainers.
• Create/update unit or integration tests for verifying the changes made.
• Follow our coding conventions.
• Add required Swagger annotation and update API documentation at fineract-provider/src/main/resources/static/legacy-docs/apiLive.htm with details of any API changes
• This PR must not be a "code dump". Large changes can be made in a branch, with assistance. Ask for help on the developer mailing list.

Your assigned reviewer(s) will follow our guidelines for code reviews.

[Aman-Mittal]

Will try to review it by eod.

…

On Fri, 24 Apr, 2026, 1:41 pm Adam Saghy, ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In .github/workflows/build-mariadb.yml <#5799?email_source=notifications&email_token=AHV6TA56O5T4V54TXE4U4R34XMOR3A5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTIMJWHA4TKNZVGM42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJL3QOJPXEZLWNFSXOX3DNRUWG2Y#discussion_r3136341803> : > permissions: contents: read jobs: test: + if: ${{ github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository }} @Aman-Mittal <https://github.com/Aman-Mittal> Let me know if you need more information. — Reply to this email directly, view it on GitHub <#5799?email_source=notifications&email_token=AHV6TA7WHNEDO2XSXAVPWGD4XMOR3A5CNFSNUABKM5UWIORPF5TWS5BNNB2WEL2QOVWGYUTFOF2WK43UKJSXM2LFO4XTIMJWHA4TKNZVGM42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJPLQOJPXEZLWNFSXOX3ON52GSZTJMNQXI2LPNZZV6Y3MNFRWW#discussion_r3136341803>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHV6TA7KKTC4DC2FRRGU7DD4XMOR3AVCNFSM6AAAAACYDZ6B4CVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHM2DCNRYHE2TONJTHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[adamsaghy]

Fixed

[Aman-Mittal]

@adamsaghy

All failed runs seems to giving cache miss error
enableCrossOsArchive: false
lookup-only: false
env:
DEVELOCITY_ACCESS_KEY:
IMAGE_NAME: fineract
BASE_URL: https://localhost:8443
TEST_USERNAME: mifos
TEST_PASSWORD: password
TEST_STRONG_PASSWORD: A1b2c3d4e5f$
TEST_TENANT_ID: default
INITIALIZATION_ENABLED: true
EVENT_VERIFICATION_ENABLED: true
ACTIVEMQ_BROKER_URL: tcp://localhost:61616
ACTIVEMQ_TOPIC_NAME: events
JAVA_HOME: /opt/hostedtoolcache/Java_Zulu_jdk/21.0.11-10/x64
JAVA_HOME_21_X64: /opt/hostedtoolcache/Java_Zulu_jdk/21.0.11-10/x64
Error: Failed to restore cache entry. Exiting as fail-on-cache-miss is set. Input key: fineract-compiled-Linux-24918448689-3

[Aman-Mittal]

@adamsaghy It seems The caches generated by your CI generating is ranging from 400MB to 900MB each which will likely overload cache of this repo at scale.

[adamsaghy]

@adamsaghy

All failed runs seems to giving cache miss error enableCrossOsArchive: false lookup-only: false env: DEVELOCITY_ACCESS_KEY: IMAGE_NAME: fineract BASE_URL: https://localhost:8443 TEST_USERNAME: mifos TEST_PASSWORD: password TEST_STRONG_PASSWORD: A1b2c3d4e5f$ TEST_TENANT_ID: default INITIALIZATION_ENABLED: true EVENT_VERIFICATION_ENABLED: true ACTIVEMQ_BROKER_URL: tcp://localhost:61616 ACTIVEMQ_TOPIC_NAME: events JAVA_HOME: /opt/hostedtoolcache/Java_Zulu_jdk/21.0.11-10/x64 JAVA_HOME_21_X64: /opt/hostedtoolcache/Java_Zulu_jdk/21.0.11-10/x64 Error: Failed to restore cache entry. Exiting as fail-on-cache-miss is set. Input key: fineract-compiled-Linux-24918448689-3

Reworked and fixed. Thank you!

[Aman-Mittal]

Seems Ok now.

[Aman-Mittal]

@adamsaghy Seems ok now. I have also rebased the PRs properly. When those Prs give similar results feel free to resolve my comments and merge

[adamsaghy]

@adamsaghy Seems ok now. I have also rebased the PRs properly. When those Prs give similar results feel free to resolve my comments and merge

What is the expected outcome?

[Aman-Mittal]

@adamsaghy Seems ok now. I have also rebased the PRs properly. When those Prs give similar results feel free to resolve my comments and merge

What is the expected outcome?
Ideally, it should happen like this, test case PR must fail or pass similarly to their original PRs,

I have raised 2 prs that must pass and 2 that must fail.
(If they are failing due to flaky test case try rerunning those again).

[Aman-Mittal]

@adamsaghy rerun the flaky test case in adamsaghy#4
All other PRs is working as expected. And this is also working as expected but seems to failing not because of your code. Needs more digging.
But i definitely say your PR is ready for merge now.