Does not cache maven dependencies if job failed

[kool79]

I have a job which execute automated tests.
Tests are written in Java with maven.
So I want to use maven cache to reduce tests startup time.
But if my tests failed, cache is not saved.

[chiranjib-swain]

Hello @kool79 ,
Thank you for creating this issue. We will investigate it and get back to you as soon as we have some feedback.

[lmvysakh]

Hi @kool79 ,

Thanks for reporting this issue. We have investigated on this and to help address the Maven cache not being saved when tests fail, you can use the continue-on-error: true option for your test step in the GitHub Actions workflow. By enabling this, even if the mvn test step fails, the job continues to execute subsequent steps—including post-job routines like caching dependencies.

This ensures that:

• The cache save step runs even in failure scenarios.
• Other important workflow steps after the tests (such as reporting, notifications, or cleanup) will also be executed.

Example usage:

- name: Run Maven tests
  run: mvn test
  continue-on-error: true

You can read more about this feature in the official documentation:
GitHub Actions: continue-on-error

With continue-on-error: true, the workflow does not stop at a failed test, helping maintain cache consistency and speeding up future runs regardless of test outcomes, thereby resolving the issue.

To further diagnose and help resolve your issue, could you please share links to your relevant workflow runs and any additional details such as public repository links. Having this information will help us better understand your scenario and suggest tailored solutions.

Let me know if you need further assistance!