Air-gapped test lab. No proxy to configure, no mirror to point at — the machines genuinely have no route out, and files arrive on a reviewed share.
What I am trying to work out is what the complete set of artifacts is. The packages I can stage. The browser engine cache I assume I can copy from an identical machine, since it is a shared cache keyed per build. What I cannot tell from the docs is whether anything in the install or the first run reaches out on its own beyond those two.
Has anyone actually done this end to end? I would rather hear it from someone who has than discover the third thing on the day.
asked by Jide Okonkwo