Hi, > 1) Redirect to pull the list directly off my CI server. That would be 44K > per install (actually 88K since it gets pulled once by the Installer UI > and again by the Ant script. That might turn out to be more bandwidth > than I would like to support. > 2) Do #1, but move the MD5Checker task to build.a.o. The problem is that > it is an AIR app, so I think I’d just be trading one headache for another > since we can’t get to the builds.a.o machine directly to deal with AIR > updates. > 3) Request an Azure VM from Infra and move MD5Checker there. > 4) Hack something in the Installer to override the MD5s by pulling a small > file containing just the MD5s from the CI server. This would not help > folks using Ant and not the installer.
IMO it would be best if this is on Apache infrastructure as having an external dependancy is a risk. The risk being that it can stop any installs via the installer from working. Is that correct? If we do go down that path then it would be best to have it fail in a graceful way i.e. carry on the best it can if that sever (for whatever reason) can’t be reached. Thanks, Justin
