-
-
Notifications
You must be signed in to change notification settings - Fork 367
[CI] Cache Composer dependencies #2882
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
Conversation
concurrency: | ||
group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }} | ||
cancel-in-progress: true | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've found functional tests were not canceled when pushing a new commit when they are already running.
d1aa3a2
to
ec5420a
Compare
ec5420a
to
04b575a
Compare
Doesn't |
I started to remove ramsey/composer-install in #2780 because I thought it silenced errors when composer failed to install (or update IIRC) dependencies, but I was wrong, the raw Maybe the most clever thing to do here is to re-add ramsey/composer-install everywhere. WDYT? |
I always use to avoid cache complexity |
We can add a custom cache key if we need it: https://github.com/ramsey/composer-install?tab=readme-ov-file#custom-cache-key |
I'm closing this PR, I will re-open a new one |
…e (Kocal) This PR was squashed before being merged into the 2.x branch. Discussion ---------- [CI] (Re-)use ramsey/composer-install action when possible | Q | A | ------------- | --- | Bug fix? | no | New feature? | no <!-- please update src/**/CHANGELOG.md files --> | Docs? | no <!-- required for new features --> | Issues | Fix #... <!-- prefix each issue number with "Fix #", no need to create an issue if none exist, explain below instead --> | License | MIT <!-- Replace this notice by a description of your feature/bugfix. This will help reviewers and should be a good start for the documentation. Additionally (see https://symfony.com/releases): - Always add tests and ensure they pass. - For new features, provide some code snippets to help understand usage. - Features and deprecations must be submitted against branch main. - Update/add documentation as required (we can help!) - Changelog entry should follow https://symfony.com/doc/current/contributing/code/conventions.html#writing-a-changelog-entry - Never break backward compatibility (see https://symfony.com/bc). --> Replace #2882 Commits ------- 71f9723 [CI] (Re-)use ramsey/composer-install action when possible
Following #2780 (comment).
Also, sometimes the CI fails because Composer is not able to download files (e.g.: https://github.com/symfony/ux/actions/runs/15955763737/job/45001822817?pr=2880):