#36794: Cache python dependencies on GitHub Actions
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Nilesh
Type: | Pahari
Cleanup/optimization | Status: closed
Component: Core (Other) | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* has_patch: 1 => 0
* needs_better_patch: 1 => 0
* resolution: => wontfix
* status: assigned => closed
Comment:
This turned out to be more subtle than I expected.
We ''were'' using `cache: 'pip'`, so we ''were'' availing ourselves of
cached wheels. As detailed on Adam's blog post, the potential optimization
here is about not moving the wheels into place and not checking for
updated dependencies, which an application with exact pins wouldn't need
to do. We don't pin. I didn't have this internalized when writing the
ticket.
Nilesh did a great job applying my feedback, but after the latest round I
realized we had two different patterns to maintain -- one for PRs, and
another on pushes to main to get "canary" testing of breakages in latest
dependencies -- but on top of that, I realized we'd want to evict the
caches at some point. After a month? Write a new cache-eviction job, or
use the month in the cache key?
I ran this by Natalia and we agreed that the complexity/maintenance
tradeoff was starting to get worse here. So our recommendation is to do
nothing for now.
Thanks Nilesh for the investigation.
--
Ticket URL: <https://code.djangoproject.com/ticket/36794#comment:11>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019b32cef58d-73043692-f95e-4107-84ff-9ede93dc6328-000000%40eu-central-1.amazonses.com.
