Over this past weekend, we had several nightly build failures with the message sudo: cvmfs_config: command not found in the cvmfs_config setup step of this action. After finding #33, I found that manually deleting our cvmfs apt cache solved the issue. It would be nice if users didn't have to worry about this happening out of the blue. In the aforementioned issue, @vvolkl states I think it should also be possible to retry without the cache in case of errors. Can this be revisited? Or maybe a config option to delete caches with a key containing cvmfs-apt-cache in case of errors?

Link to failed build.