[wp-trac] [WordPress Trac] #53841: CI: investigate switching to the Composer cache action
WordPress Trac
noreply at wordpress.org
Fri Jul 30 21:07:47 UTC 2021
#53841: CI: investigate switching to the Composer cache action
------------------------------+-----------------------------
Reporter: jrf | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Build/Test Tools | Version:
Severity: normal | Keywords:
Focuses: |
------------------------------+-----------------------------
Follow up on/iteration inspired by #47381
There is a [https://github.com/marketplace/actions/install-composer-
dependencies 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.
[https://github.com/ramsey/composer-install/issues/164 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
--
Ticket URL: <https://core.trac.wordpress.org/ticket/53841>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list