Cache Charm Builds #78
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mateoflorido
force-pushed
the
KU-684/caching-charms
branch
4 times, most recently
from
6da3007 to
997e66e
Compare
mateoflorido
force-pushed
the
KU-684/caching-charms
branch
from
997e66e to
c6bd307
Compare
|
Everyone contributing to this PR have now signed the CLA. Thanks! |
|
so, what happens if one of the deps in requirements.txt changes? The hash would still match right? How do we pick up new changes of python dependencies? |
mateoflorido
force-pushed
the
KU-684/caching-charms
branch
from
3569059 to
7611260
Compare
No, we are hashing the |
mateoflorido
force-pushed
the
KU-684/caching-charms
branch
from
4ebe88d to
3b7038a
Compare
addyess
approved these changes
Apr 24, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
This pull request introduces a caching mechanism for charms. If there are no changes in the source of the charm or its dependencies, the workflow restores the cached charms. This reduces integration test times by around 80%. This is particularly useful when tweaking the testing suite or other files that are not dependent on the charm sources.