-
Notifications
You must be signed in to change notification settings - Fork 91
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
Use caching CI builds #753
Comments
Hello @mbrandenburger, can I start working on this? |
Hi @osamamagdy, yes please give it a try. |
Thanks @mbrandenburger. I started by investigating how to solve the issue. Here is what I found:
|
Would this approach affect the running container by any means? like it would fail tests for some reason? |
This looks like the right direction to me. 💪 In addition to the go deps, we may also think about caching other artifacts we consume (i.e., fabric binaries, docker images) |
@mbrandenburger Thanks. I am trying to activate the volume mount in the pipeline by assigning a value to DOCKER_DEV_RUN_OPTS before calling the make file like here |
@mbrandenburger It worked by adding a new variable to the make file and appending it to the DOCKER_DEV_RUN_OPTS. Is this acceptable? can you review PR #762 I will revert the changes to the workflow triggers before the changes are merged |
@osamamagdy thanks! I will look into this asap! |
I re-opened the issue to capture other options for caching. |
Thanks @osamamagdy for improving CI caching with the go mod package caching. 🚀💪🎉 |
The current CI build could be improved to leverage caching. In particular, installing software dependencies (mostly in go) is time consuming and may benefit from caching.
The text was updated successfully, but these errors were encountered: