On 12/29/15, 12:18 AM, "Justin Mclean" <justinmcl...@me.com> wrote:
>Hi, > >> The I run MD5Checker locally (it is in flex-utilities) or wait for the >>CI >> job to report the cache ID. The cache ID is the etag header. You might >> be able to sniff it some other way. > >I given up on this die to lack on documentation and the existing MD5 >checker has no way of checking a local config file as far as I can see. >If someone else want’s to try and fix this please go ahead. Again, you don't have to get the cache ID right, just the MD5 which you can test in the installer locally. The cache ID is only for MD5Checker to void having to do all of these big downloads only to find out the artifact didn't change. -Alex
