WordPress.org

Make WordPress Core

Opened 8 weeks ago

#53841 new enhancement

CI: investigate switching to the Composer cache action

Reported by: jrf Owned by:
Milestone: Awaiting Review Priority: normal
Severity: normal Version:
Component: Build/Test Tools Keywords:
Focuses: Cc:

Description

Follow up on/iteration inspired by #47381

There is a Composer caching action available via the GitHub marketplace.

This action is already in use in the code style and PHPCompatibility workflows, but not yet in the unittest and code coverage action workflows.

Switching over to that action, would allow for further simplification of the workflow scripts as we would be able to replace four steps in each workflow with one.

Whether or not we can switch over, depends on how fine-grained the cache key is which is created by the action.

An issue has been opened asking for more details about the information used in the cache key generated by the action and is currently waiting for an answer.

The various requirements we have for a cache key are discussed in more detail in the PR which addressed #47381 - GitHub: https://github.com/WordPress/wordpress-develop/pull/1511#discussion_r674130418

Change History (0)

Note: See TracTickets for help on using tickets.