Hunter wrote: What if that timestamp was based upon the scm's last commit timestamp > instead of the time of the build? >
Folks: remember that Subversion works differently to Git. With subversion there's no hash, just an integer that goes up constantly for everything in the larger repo. Your trunk/master/release-branch may not have changed in 10 mins, but the repo might have done for an unrelated project/dir. You're best to make a merkle tree for all files in the checkout (ignoring target/). You can do that with Subversion too of course even though it does not itself maintain a Merkle tree of the current set of files nor the history (as Git goes). Full disclosure - I am obsessed with Merkle trees (but not blockchain).
