Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI] Adjust composer cache key hash to account for composer.lock removal #1538

Closed
wants to merge 1 commit into from

Conversation

rosier
Copy link
Contributor

@rosier rosier commented Nov 10, 2024

No description provided.

javiereguiluz added a commit that referenced this pull request Jan 3, 2025
This PR was merged into the main branch.

Discussion
----------

Remove the composer cache from the CI workflows

I think there is little benefit anymore for this repository to have a composer cache in the CI workflows. With composer v2 the dependencies are downloaded in parallel which is a lot faster than composer v1. This makes the performance gains from the cache small since it also takes time to setup and save or restore the cache.

Also the chance for a cache hit is low:
- This repository has low traffic and the cache expires after a week which reduces the chance for a cache hit.
- Every branch / PR get it's own cache which again reduces the chance for a cache hit.

So I purpose to remove the composer cache to simplify the workflows.

Replaces: #1538

Commits
-------

a4baa11 Remove the composer cache from the CI workflows
@javiereguiluz
Copy link
Member

Let's close this in favor of #1551, which removes the GitHub cache entirely because it's not that useful to us. Thanks!

@rosier rosier deleted the cache-hash branch January 3, 2025 16:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants