I have a rails app that compiles assets as part of the test suite. What was working before is no longer working: steps: - checkout - run: mkdir -p tmp/test/cache/assets - attach_workspace: at: ~/fworkspace - run: tar -cf - app/assets | md5sum > asset_checksum.txt …

This wasn’t relevant. Tar is taking into account more than just file contents, like creation date and other meta datawhich would be different on each checkout. Ended up going with an alternative.

find app/assets -type f -exec md5sum {} \; | sort -k 2 | md5sum > asset_checksum.txt

Using a checksum to identify a unique directory

Build Environment Running Tests

Kurt-von-Laven May 16, 2021, 2:52am 3

Checksum different before and after bundle install - #11 by PADomine or Caching Dependencies - CircleCI may address the issue you encountered, @abe.

Topic		Replies	Views
Caching based on the checksum of a directory's contents Tips, Tricks, and Hacks caching	2	8124	May 16, 2021
Checksum different before and after bundle install Build Environment bundler , config	14	9113	December 14, 2018
Checksums doesn't match Feedback & Bug Reports	8	3551	July 23, 2018
How to interact with checksum of cache restored dependency file? Caching Dependencies cache	1	2193	March 7, 2019
Can not RUN rails assets:precompile on my build when use cache vendor/bundle Caching Dependencies	0	4601	August 21, 2019

Using a checksum to identify a unique directory

Related topics