You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if the cache exists at the start of the job, it is not updated with any changes to the target directory that happen during the job.
We have a moderately complicated workspace with a bunch of different crates, which get built and tested via a matrix job. The crates have plenty of shared dependencies - so it would be nice for them to benefit from a shared cache - but also some that are not shared. What we find is that the first job to run creates the cache with the dependencies for that job, but subsequent jobs do not update the cache, so their dependencies are never cached.
The text was updated successfully, but these errors were encountered:
Currently, if the cache exists at the start of the job, it is not updated with any changes to the
target
directory that happen during the job.We have a moderately complicated workspace with a bunch of different crates, which get built and tested via a matrix job. The crates have plenty of shared dependencies - so it would be nice for them to benefit from a shared cache - but also some that are not shared. What we find is that the first job to run creates the cache with the dependencies for that job, but subsequent jobs do not update the cache, so their dependencies are never cached.
The text was updated successfully, but these errors were encountered: