[ci] Generate a different cache key for every job #181
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.
Without this fix every job was using essentially the same cache key, which meant that they were all using the cache uploaded by the first runner to finish whenever we made some changes to
Cargo.toml
.This fix should in theory yield a nice performance boost, especially on jobs that are particularly slow, like when
compact_filters
is enabled.If this works out, we can close #157 because after the first run the compiled
librocksdb-sys
should stay cached for all the subsequent ones.