Remove Outdated Cache Restore Step in Maven (Legacy) Release Workflow

[victoralfaro-dotcms]

User Story

As a platform engineer, I want to remove a step for restoring cache using an outdated key in the Maven (legacy) release process workflow, so that the release pipeline is more efficient and avoids unnecessary cache retrieval.

Acceptance Criteria

• Identify and remove the cache restore step that uses an outdated key.
• Ensure the release workflow functions correctly without the removed step.

dotCMS Version

main

Proposed Objective

Quality Assurance

Proposed Priority

Priority 2 - Important

External Links... Slack Conversations, Support Tickets, Figma Designs, etc.

to_define

Assumptions & Initiation Needs

• Understanding of the current Maven (legacy) release workflow.
• Access to CI/CD pipeline configurations.

Quality Assurance Notes & Workarounds

• Ensure that cache removal does not introduce build failures or regressions.
• Test with multiple release runs to confirm expected behavior.

Sub-Tasks & Estimates

1. Analysis: Review current cache restore step and identify the outdated key usage. Estimate: 1 day
2. Implementation: Remove the unnecessary step and update the workflow. Estimate: 2 days

[github-actions]

PRs:

• #31452: removing fallback restore keys for release process #31453