-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Setup Drone cache #3146
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
Comments
cc/ @liufengyun |
We could maybe work around the issue by lunching the first sbt instance "as is", and for the 3 other do
|
Drone will update the cache with what's in |
Maybe we could add another sbt instance just for that, ie |
I believe the cache is already implemented. When the Docker image is created, it builds the cache by calling This command will run the test suite /cc @smarter |
Drone caching is not implemented. The point of setting up Drone caching is to not have to update the Docker image every time dependencies change. |
So the idea is to not store the deps in the image itself but have a separate cache independent from the image, which the image accesses? |
Exactly. For example, drone-volume-cache is a plugin that uses a volume on the host machine for the cache. |
Closing as we're migrating to github actions which has a caching mechanism: #8353 |
Here is my take at setting up a cache for Drone: dotty-staging@345cf90
The issue is that we have four instances of sbt running in parallel sharing the same cache. When there is nothing to update everything works fine but if sbt tries to update the ivy2 cache, it fails with the following exception:
Stacktrace
So for now, we don't have a better solution than updating the docker image every time a dependency is updated.
The text was updated successfully, but these errors were encountered: