Hi, All
One point I noticed is that the log in url is hard coded with "http://validation.linaro.org/lava-server/accounts/login/". but the url written in lava-job-info is "https://validation.linaro.org/lava-server%22(http://staging.validation.linar... when submitted to staging)
If we use the url that written in lava-job-info to do the redirect, I guess it will ask the user to add the certificates explicitly.
Thanks, Yongqin Liu
On 22 August 2012 01:53, Andy Doan andy.doan@linaro.org wrote:
On 08/21/2012 10:45 AM, James Tunnicliffe wrote:
On 21 August 2012 16:19, Zach Pfeffer zach.pfeffer@linaro.org wrote:
On 20 August 2012 22:35, YongQin Liu yongqin.liu@linaro.org wrote:
On 21 August 2012 10:25, YongQin Liu yongqin.liu@linaro.org wrote:
Hi, Paul
I have tried with the Shift+Reload and Ctrl+R about 10 times for each, but the problem still exists. I have reported it as a bug here: https://bugs.launchpad.net/linaro-android-infrastructure/+bug/1039319
I found the reason. We need to access the https://validation.linaro.org/lava-server via FireFox, and add the exception trust(not remember the exact name:() for it, after that we can see the lava result on the page then.
Oh wow that's a bit convoluted.
Andy, it sounds like we just need to put some instructions together to point people to the build test results. Do you have any instructions like that?
It sounds like the proper solution would be to get some SSL certificates. These need not cost us anything if we got individual certs for each subdomain, but for the sake of $60 we could get a cert to cover *.linaro.org and solve a lot of HTTPS warnings: https://www.startssl.com/?app=40
+1 - its nuts we haven't done this already