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

Using caching in CircleCI to optimize workflow. #41

Merged
merged 4 commits into from
Jan 17, 2022

Conversation

dribeiro-ShardLabs
Copy link
Contributor

Optimized CircleCI workflow to use caching

.circleci/config.yml Outdated Show resolved Hide resolved
.circleci/config.yml Show resolved Hide resolved
.circleci/config.yml Outdated Show resolved Hide resolved
scripts/test.sh Outdated Show resolved Hide resolved
- &restore_cairo_cache
- restore_cache:
name: "Restore cairo-lang Cache"
key: cairo-lang-cache-{{ arch }}-{{ checksum "/tmp/cairo-lang-version" }}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've given this some more thought. There's a danger in doing this in case plugin's not yet been adapted to work with the latest version. This is clear if we observe the setup-venv script which has the plugin version hardcoded.

The ideal approach would be to have the current cairo-lang to which the plugin is adapted only in one place, but so far we haven't been able to come up with that.

Probably we'll have to hardcode it here as well. That way we'll have two more places (restore and save) to change when adapting to new cairo-lang versions (there are a few already across the project, e.g. Readme). Or in case we can utilize variables config.yml, there'd only be one more place.

@dribeiro-ShardLabs dribeiro-ShardLabs merged commit 79c1202 into master Jan 17, 2022
@FabijanC FabijanC deleted the circleci-cache branch May 6, 2022 12:03
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.

None yet

2 participants