In testing out some of the release process for loop standalone, it was realised that being able to test the standalone side against the direct addresses for the elastic load balancers would be useful. This would allow the tests to be run against production before a dns switch. I think the work we need to do here boils down to: - Allow the loop standalone URL to be set - Turn off certification checking for mismatches (the elbs have addresses that don't match hello.firefox.com).
Comment on attachment 8727846 [details] [review] [loop] Standard8:bug-1254511-elb > mozilla:master Ok, so it appears that its not possible to set up Firefox/Marionette to easily run against pages with domain name mismatches on the certs. Hence, we can't actually do too much here because of the setup. The best we can do for pre-release is suggest to alter the hosts file to point to the right directory. We still need to land the loop.linkClicker.url pref change, as that means we can do: TEST_SERVER=prod USE_LOCAL_STANDALONE=0 make functional and have everything pass. I've filled a follow-up bug for making it work even nicer. I also think landing the additional CONTENT_SERVER_URL as an optional environment variable is potentially useful as well - it allows us to easily test different loop-server & standalone combinations should we need to at some stage.
Attachment #8727846 - Flags: review?(dcritchley) → review+
Status: NEW → RESOLVED
Iteration: --- → 48.1 - Mar 21
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.