-
-
Notifications
You must be signed in to change notification settings - Fork 191
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
CircleCI: seperate caches based on core modules measurements #769
Comments
Note: not only modules should be measured to create a distinct cache key (generation/extraction in CIs), but also the patches linked to modules, else they will never be applied. So the best key would probably be:
This simple CI hack would speed up rebuilding most Heads changes, which are mostly scripts. |
This ticket priority just got promoted since #795 requires a cache of coreboot 4.11 (with more patches coming) while other platforms requires a cache of coreboot 4.8.1 with different patches being applied.... Will try to wrap my head around https://app.circleci.com/pipelines/github/tlaurion/heads?branch=CircleCI_specialized_caches and add #769 (comment) requirements... As of right now, cache needs to be cleared up which makes each remote build of more then 2+hours each... |
Second attempt here: Failing result here: https://app.circleci.com/pipelines/github/tlaurion/heads/283/workflows/b3f64a9b-25f9-4194-9884-849a1fd9f897/jobs/308
|
Went successful. Optimizing and testing happening here: https://app.circleci.com/pipelines/github/tlaurion/heads/291/workflows/dede686d-5aee-4928-9ef8-19f36942f6a3/jobs/316 |
Work done on CircleCI will be paid by https://opencollective.com/insurgo and this ticket will be updated with bounty payment details being cross-referenced. |
Commits linked to invoice of 2000$ at opencollective (cannot do this for free anymore...) |
The idea here (to replicate on #768 GitlabCI):
That way:
As of right now, the cache is made a single time and never remade, based on:
and
Failed attempts to specialize CircleCI caches happened here
The text was updated successfully, but these errors were encountered: